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

Flaky CI related investigation and fixes #1280

Merged
merged 7 commits into from
Jan 30, 2025
Merged

Flaky CI related investigation and fixes #1280

merged 7 commits into from
Jan 30, 2025

Conversation

vigoo
Copy link
Contributor

@vigoo vigoo commented Jan 30, 2025

  • Adds the cargo parallel job limit to the cli-tests step too
  • Reenables parallel test execution and jUnit reporting
  • Updates to the latest test-r which writes out partial jUnit reports after each test (so we get some info even if the CI run times out)
  • Adds a timeout to the js-3 worker executor test
  • Most importantly moves the epoch tick calls to a separate thread. This is what intrerrupts wasm execution and makes sure the system can yield to other tokio tasks during long-running wasm code. As the tick calls were accidentally also scheduled as tokio tasks, it could not make itself work when the system got overloaded. By moving this to a dedicated separate background thread we no longer have this problem.

@vigoo vigoo enabled auto-merge (squash) January 30, 2025 18:49
@vigoo vigoo merged commit 82bd98e into main Jan 30, 2025
19 checks passed
@vigoo vigoo deleted the flakyness branch January 30, 2025 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants