Drupal\Tests\Composer\Plugin\VendorHardening\ConfigTest leaking configuration changes.

Pretty sure I figured out what's causing this. I'll follow up with some documentation but the details are mostly in the summary. Mostly you just need to run phpunit directly and you see the failure. If you run run-tests which splits everything into its own process you won't.

Yes, one test must be modifying a file and not correctly cleaning itself after the test. This leaked test data is then contaminating a future test.

woops, got distracted and didn't follow up on those notes and lost all my changes from debugging this. From memory, ConfigTest::testMixedCaseConfigCleanupPackages was interacting with the global composer instance or something. The simple fix was just adding @runInSeparateProcess to the test and I think that resolved it.

Well hello old me. Found this again testing PHPUnit 10 changes. Don't think its technically currently a blocker but gets in the way of testing so would be good to get out of the way since its such an easy fix.

Simple fix, updated issue summary to include proposed fix.

Committed to 11.x and backported to 10.2.x

Nice find, simple fix

larowlan → closed merge request !5624

Automatically closed - issue fixed for 2 weeks with no activity.