New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unstable test EmbeddedSubProcessTest.shouldNotTriggerBoundaryEventWhenFlowscopeIsInterrupted
#11844
Comments
We should tackle flaky tests as soon as we can. Marking as |
ZPA Planning:
|
It seems that this unit test is still flaky. It failed a few times on this PR: https://github.com/camunda/zeebe/actions/runs/5134009576/jobs/9237391641 Perhaps it is worth to reopen this issue, or should we see if it happens in more places? wdyt @oleschoenburg |
Let's reopen so ZPA is aware and can look into it if they want to. I'm not sure if this is just flakiness or a potential bug. |
Moving flaky tests immediately into ready, because these are always urgent. |
Over the last days I ran this about 12k times without failure. As I don't have access to the test reports of the CI anymore I don't really have any options to debug this any further. Because of this I will close this now. Might it still be flaky? Sure. If someone in the future encounters a run where this is flaky please reopen it. It would also help if the test reports are attached, so it doesn't matter if they expire. |
13497: Resolve flaky EmbeddedSubProcessTest r=remcowesterhoud a=remcowesterhoud ## Description <!-- Please explain the changes you made here. --> This test contained a race condition as it was depending on a specific timing of message correlations. This commit changes this test to use error events instead. The behavior is the same, but this should make it deterministic. In other versions the test was moved to a different class. I will make a separate PR for this with back ports. This only for stable/8.0. ## Related issues <!-- Which issues are closed by this PR or are related --> closes #11844 Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
Summary
Failures
Example assertion failure
Hypotheses
Logs
https://github.com/camunda/zeebe/actions/runs/4289453228/jobs/7472507432
https://github.com/camunda/zeebe/actions/runs/4290687672/jobs/7475272618
https://github.com/camunda/zeebe/actions/runs/4293686871/jobs/7481685355
The text was updated successfully, but these errors were encountered: