Skip to content

Commit ce6b58e

Browse files
committed
Add CI probe — run only the 3 failing tests in isolation
UDF-augmented PDO churn (raw open/close 0..500 with 44 UDFs each) also doesn't reproduce either bug. The triggering state must be something the actual driver does in earlier tests. Run a filtered PHPUnit invocation that exercises *only* the three failing tests (no preceding suite). If they pass alone, the bug is absolutely from prior tests' state buildup; if they fail alone, it's intrinsic to the test setup. Either result narrows the search.
1 parent 96c7ba0 commit ce6b58e

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

.github/workflows/phpunit-tests-turso.yml

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1995,6 +1995,22 @@ jobs:
19951995
# form crashes testReconstructTable. Test stays failing.
19961996
PY
19971997
1998+
- name: Probe — run only the 3 failing tests via PHPUnit filter
1999+
continue-on-error: true
2000+
env:
2001+
LD_PRELOAD: ${{ steps.preload.outputs.value }}
2002+
working-directory: packages/mysql-on-sqlite
2003+
run: |
2004+
set +e
2005+
# If only the 3 failing tests are run (no preceding suite), do
2006+
# they still fail? This isolates whether the bug is intrinsic
2007+
# to the tests or accumulated from prior tests.
2008+
timeout --kill-after=10 120 \
2009+
php ./vendor/bin/phpunit -c ./phpunit.xml.dist \
2010+
--filter '(testCreateTemporaryTable|testTemporaryTableHasPriorityOverStandardTable|testInformationSchemaTablesFilterByAutoIncrement)' \
2011+
--debug 2>&1 | tail -50
2012+
echo "(probe step: continue-on-error)"
2013+
19982014
- name: Run PHPUnit tests against Turso DB
19992015
env:
20002016
LD_PRELOAD: ${{ steps.preload.outputs.value }}

0 commit comments

Comments
 (0)