ProcesExecutionRandomizedPropertyTest:shouldExecuteProcessToEnd is flaky #11121
Assignees
Labels
kind/bug
Categorizes an issue or PR as a bug
kind/flake
Categorizes issue or PR as related to a flaky test
version:8.1.6
Marks an issue as being completely or in parts released in 8.1.6
version:8.2.0-alpha3
version:8.2.0
Marks an issue as being completely or in parts released in 8.2.0
Comments
deepthidevaki
added
the
kind/flake
|
Seeds: processSeed=2036895956970042930, executionPathSeed=1685396434835304029 relevant logging |
|
My quick initial analysis
|
|
happened another time TestDataRecord{processSeed=4020342130641592473, executionPathSeed=7049668446223977370 logs |
|
Failed again: https://github.com/camunda/zeebe/actions/runs/3601529537/jobs/6067440685 |
|
Failed on main again https://github.com/camunda/zeebe/actions/runs/3602288680/jobs/6069069535 @saig0 @korthout @koevskinikola @remcowesterhoud are you working on this? |
|
Assuming the issue is the same here as I described in #11121 (comment), yes. I will fix it on Monday. |
|
Thanks @remcowesterhoud 👍 |
remcowesterhoud
added a commit
that referenced
this issue
Dec 2, 2022
We have a bug in Zeebe. This escalation block builders makes it so there is a high chance that we run into this bug. For now let's disable this until the bug is fixed. #11121 (comment)
9 tasks
ghost
pushed a commit
that referenced
this issue
Dec 2, 2022
11166: Temporarily disable escalation events in process generation r=remcowesterhoud a=remcowesterhoud ## Description <!-- Please explain the changes you made here. --> We have a bug in Zeebe. This escalation block builders makes it so there is a high chance that we run into this bug. For now let's disable this until the bug is fixed. #11121 (comment) ## Related issues <!-- Which issues are closed by this PR or are related --> Related to #1121 Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
9 tasks
ghost
pushed a commit
that referenced
this issue
Dec 7, 2022
11178: Interrupt flow scope when a terminate end event is reached r=koevskinikola a=remcowesterhoud ## Description <!-- Please explain the changes you made here. --> The terminate end event should mark its flow scope as interrupted when it's completed. Having an interrupted flow scope means other elements in this scope can no longer be activated or completed. Any ACTIVATE/COMPLETE command will be rejected. If we do not interrupt the flowscope it is possible for the engine write a TERMINATE command as a result of the end event. It could then go on to process a COMPLETE command. This will not be rejected, and it will take outgoing sequence flows for this element. The TERMINATE will then be rejected as the element is no longer active. Since the flowscope now has an outgoing sequence flows it is considered to have active elements, it will not be terminated, as it should upon reaching a terminate end event. Since the flow scope gets interrupted we will also have to change the logic in the processors of these possible flow scopes (`ProcessProcessor`, `SubProcessProcessors`, `EventSubProcessProcessor`). Here we need to verify that the scope was interrupted by a terminate end event, and if it is we need to make sure the scope gets completed, instead of terminated. ## Related issues <!-- Which issues are closed by this PR or are related --> relates to #11121 Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
ghost
pushed a commit
that referenced
this issue
Dec 7, 2022
ghost
pushed a commit
that referenced
this issue
Dec 7, 2022
9 tasks
ghost
closed this as 
Merged
14 tasks
Zelldon
added
the
version:8.1.6
npepinpe
added
the
version:8.2.0
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failures
Logs
Test results for Property Tests.zip
The text was updated successfully, but these errors were encountered: