Hi Joseph,
kanboard is currently preventing migration of symfony to testing.
https://qa.debian.org/excuses.php?package=symfony
The relevant test failure is the following.
▾ test upstream: test run
67s autopkgtest [08:29:27]: test upstream: [-----------------------
67s phpab %development% - Copyright (C) 2009 - 2026 by Arne Blankerts and Contributors
67s
67s Scanning directory tests/units
67s
67s Autoload file autoload.tests.php generated.
67s
68s Proceeding without a composer.json file.PHPUnit 13.0.0 by Sebastian Bergmann and contributors.
68s
68s Runtime: PHP 8.4.16
68s Configuration: /tmp/autopkgtest-lxc.z2g8f66q/downtmp/autopkgtest_tmp/tests/units.sqlite.xml
68s
94s ............................................................. 61 / 1147 ( 5%)
121s ............................................................. 122 / 1147 ( 10%)
146s ............................................................. 183 / 1147 ( 15%)
172s ............................................................. 244 / 1147 ( 21%)
197s ............................................................. 305 / 1147 ( 26%)
219s ............................................................. 366 / 1147 ( 31%)
246s ............................................................. 427 / 1147 ( 37%)
272s ............................................................. 488 / 1147 ( 42%)
297s ............................................................. 549 / 1147 ( 47%)
318s ..............................................F
318s
318s Time: 04:10.131, Memory: 44.00 MB
318s
318s There was 1 failure:
318s
318s 1) KanboardTests\units\Job\SubtaskEventJobTest::testTriggerEvents
318s Failed asserting that actual size 4 matches expected size 5.
318s
318s /tmp/autopkgtest-lxc.z2g8f66q/downtmp/autopkgtest_tmp/tests/units/Job/SubtaskEventJobTest.php:55
318s
318s FAILURES!
318s Tests: 596, Assertions: 3193, Failures: 1.
318s autopkgtest [08:33:38]: test upstream: -----------------------]
I’ve noticed the presence of a new upstream release, but am unsure the
issue will get fixed with it. Can you please have a look and figure out
if this is an upstream issue. If the issue is narrowed to the test (and
not an actual issue with the latest symfony version), can you please
workaround or disable it?
Thanks in advance,
taffit