From 3afaa65672ce97db07591883340cee2f882cd02f Mon Sep 17 00:00:00 2001 From: Darko Gjorgjijoski Date: Sat, 22 Aug 2026 15:05:12 +0200 Subject: [PATCH] ci: keep the isolated test group out of the parallel pass Passing --exclude-group on the command line overrides the phpunit.xml group exclusions, so the parallel CI pass was running the isolated database-refusal test inside a shared worker and poisoning its siblings (VACUUM inside a transaction, duplicate migrations table) - flakily, depending on sharding. Exclude it explicitly and run it serially like the other quarantined groups. --- .github/workflows/check.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/check.yaml b/.github/workflows/check.yaml index 46f7054d..042d3555 100644 --- a/.github/workflows/check.yaml +++ b/.github/workflows/check.yaml @@ -101,9 +101,12 @@ jobs: uses: ramsey/composer-install@4.0.0 - name: Apply tests ${{ matrix.php-version }} (parallel) - run: php artisan test --parallel --exclude-group=modules --exclude-group=architecture + # CLI --exclude-group overrides the phpunit.xml exclusions, so the + # isolated group must be re-excluded here or it poisons a worker. + run: php artisan test --parallel --exclude-group=modules --exclude-group=architecture --exclude-group=isolated - - name: Apply module and architecture tests ${{ matrix.php-version }} (serial) + - name: Apply module, architecture and isolated tests ${{ matrix.php-version }} (serial) run: | php artisan test --group=modules php artisan test --group=architecture + php artisan test --group=isolated