Problem/Motivation
when trying to test an issue fork I'm getting errors that this test failed.
Running the unmodified branch of the module it has the same errors:
https://git.drupalcode.org/issue/queue_ui-3494639/-/jobs/5977081
There were 6 errors:
1) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronNegativeValue
Test was run in child process and ended unexpectedly
2) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronEmptyValue
Test was run in child process and ended unexpectedly
3) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronZeroValue
Test was run in child process and ended unexpectedly
4) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronOneValue
Test was run in child process and ended unexpectedly
5) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronPositiveValue
Test was run in child process and ended unexpectedly
6) Drupal\Tests\queue_ui\Functional\CronTimeLimitChangeTest::testSetCronStringValue
Test was run in child process and ended unexpectedly
Steps to reproduce
Run the project in Drupal CI to verify the failure
This failure doesn't happen locally if I directly invoke phpunit (using php 8.2 and Drupal 10)
The bug could relate to Drupal 11 and to the fact that this test enables the queue_ui_cron_test_fixtures module
Issue fork queue_ui-3537455
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:
Comments
Comment #2
pwolanin commentedI found the bug - there is an error in the namespace declaration for that class
Comment #4
pwolanin commentedComment #5
fjgarlin commentedChanges look good and tests are happy now. RTBC.
Comment #8
volegerFixed, thanks.
I'll publish the release later this week.