Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
Screenshot from 2026-07-24 01-12-03.png508.08 KBcatch

Issue fork drupal-3612828

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

catch created an issue. See original summary.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Needs review
catch’s picture

catch
he/him
Primary language English
commented

Benefits ComposerTaggedReleaseTest more but potentially both: https://git.drupalcode.org/project/drupal/-/jobs/11123115

catch opened merge request !16419

catch’s picture

catch
he/him
Primary language English
commented

Handling ComponentsIsolatedBuildTest in #3612922: Optimize ComponentsIsolatedBuildTest.

mstrelan’s picture

mstrelan commented

Should we also skip this in package_manager tests? Some of them are skipped, but should be updated anyway. I believe \Drupal\Tests\package_manager\Build\PackageInstallDirectWriteTest::testPackageInstall is not skipped, and AFAICT audit runs even for composer update --lock.

FWIW we already use COMPOSER_NO_AUDIT=1 in \Drupal\BuildTests\Composer\Plugin\Unpack\Functional\UnpackRecipeTest. It might be feasible to set that somewhere globally in CI? Unless of course we have tests that depend on it.

catch’s picture

catch
he/him
Primary language English
commented

@mstrelan yes it's worth doing, in profiling it adds about 3s to every operation.

Setting it globally in CI sounds good, not sure if we add it to .gitlab-ci.yml envrinment variables whether it'll successfully get set for composer but that'd probably be easiest?

catch’s picture

catch
he/him
Primary language English
commented
Status: Needs review » Closed (duplicate)

Duplicate of #3491268: Look into skipping audit of composer operations in package manager tests.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.