Problem/Motivation
Have seen this one pop up several times https://git.drupalcode.org/issue/drupal-3183509/-/jobs/4777988
Steps to reproduce
https://git.drupalcode.org/issue/drupal-3515404/-/jobs/4787495
https://git.drupalcode.org/issue/drupal-3515404/-/jobs/4787584
https://git.drupalcode.org/issue/drupal-3515404/-/jobs/4787672
Proposed resolution
Use WaitTerminateTestTrait
Remaining tasks
- Review MR
- Review fixed pipeline https://git.drupalcode.org/issue/drupal-3515404/-/jobs/4788078
- Rejoice
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3515404
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:
- 3515404-fix
changes, plain diff MR !11640
- 3515404-repeat-fix
changes, plain diff MR !11638
- 3515404-repeat
changes, plain diff MR !11635
Comments
Comment #2
acbramley commentedComment #3
mstrelan commentedSounds like state cache race condition. Probably needs
WaitTerminateTestTrait.Comment #6
mstrelan commentedRepeat 1000 times:
Run 1 - 7/1000 fails
Run 2 - 14/1000 fails
Run 3 - 10/1000 fails
With WaitTerminateTestTrait:
Run 1 - 2/1000 fails
Run 2 (after moving setWaitForTerminate) - 0/1000 fails
Run 3 - 0/1000 fails
Comment #10
mstrelan commentedI forgot to actually commit the code for Run 1 with WaitTerminateTestTrait, which is why it had 2 fails. I've moved the
setWaitForTerminatecall where I intended it to be the first time and ran it again:Run 4 - 0 fails
I've hidden the 2 test branches and opened a new branch (MR !11640) with only the fix. This is ready for review.
Comment #11
acbramley commentedMakes sense, test is specifically testing maint mode which requires state and that requires the wait trait.
I wonder if there's an easy way to find tests using state that aren't using the wait trait yet 🤔
Comment #12
larowlanThanks, committed to 11.x