Skip to content
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

Engine.waitForIdleState() does not work as expected #244

Closed
Tracked by #189
pihme opened this issue Mar 8, 2022 · 1 comment · Fixed by #248
Closed
Tracked by #189

Engine.waitForIdleState() does not work as expected #244

pihme opened this issue Mar 8, 2022 · 1 comment · Fixed by #248

Comments

@pihme
Copy link
Contributor

pihme commented Mar 8, 2022

Description

Called for here: zeebe-io/zeebe-cluster-testbench#591 (comment)

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
@pihme
Copy link
Contributor Author

pihme commented Mar 9, 2022

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.

@pihme pihme mentioned this issue Mar 9, 2022
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant