You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In that case, replacing Thread.sleep(250) with engine.waitForIdleState() causes the test to fail. Other instances have also been mentioned in the comment
Expected behaviour
waitForIdleState() does what the name suggests
Reproduction steps
Check out code referred to in comment
replace Thread.sleep(250) with engine.waitForIdleState()
Environment
OS: Linux
Version: 1.4.0-alpha2, 1.4.0-alpha3-SNAPSHOT (of March 8th)
Flakiness observed in embedded and in testcontainer setup
The text was updated successfully, but these errors were encountered:
After further analysis, the common denominator seems to be the interplay between the test engine and a worker. E.g. we reach an idle state, because the worker has not activated the job yet. But since the worker didn't activate the job yet, the assertions don't hold.
Description
Called for here: zeebe-io/zeebe-cluster-testbench#591 (comment)
In that case, replacing
Thread.sleep(250)
withengine.waitForIdleState()
causes the test to fail. Other instances have also been mentioned in the commentExpected behaviour
waitForIdleState()
does what the name suggestsReproduction steps
Thread.sleep(250)
withengine.waitForIdleState()
Environment
The text was updated successfully, but these errors were encountered: