check-examples-on-wasm CI job keeps timing out stochastically
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
See https://github.com/bevyengine/bevy/actions/runs/13751916389/job/38453938574
This appears to occur effectively at random: retrying the same merge often passes.
This is important to check so I'd really like to not remove it, but at the same time the unreliability and delay is really frustrating when trying to make changes.
@mockersf suggested to me that this may be due to instance overprovisioning causing OOM.
Contributor guide
Research direction
Start with the linked GitHub Actions run and the `check-examples-on-wasm` job, then compare failed and successful retries of the same merge. Investigate whether instance overprovisioning or OOM explains the stochastic timeout; done means the job completes reliably without removing this check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust, wasm
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100