oxidecomputer / oxidecomputer/omicron
Higher than expected packet loss in commtest in CI
Open
Nobody has claimed this yet.
networking
Test Flake
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
When running commtest in CI, I'm seeing 10%+ packet loss. I do not see this when running locally. Perhaps the control plane is still busy spinning up across the VMs when commtest is running in CI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with end-to-end-tests/src/bin/commtest.rs and compare its CI behavior with a local run. Investigate whether control-plane startup across the VMs is still in progress when commtest runs. Done means the cause of the 10%+ CI packet loss is identified and the CI run no longer exhibits unexpectedly higher loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, networking, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100