oxidecomputer / oxidecomputer/omicron
test failed in CI: test_action_failure_can_unwind_no_pantry
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This test failed on a CI run on "main":
https://github.com/oxidecomputer/omicron/runs/37400967892
https://github.com/oxidecomputer/omicron/runs/37258633618
Log showing the specific test failure:
https://buildomat.eng.oxide.computer/wg/0/details/01JMCM6ZRMXV0MZH3G7YF88PDR/5HQMqa0iK1j8Uxd3j0delSKHNqwPIaxCWJ9WCZYZdDWGvA4W/01JMCM7AVMPW3YY52VMK6YTQ8F#S6135
https://buildomat.eng.oxide.computer/wg/0/details/01JM38MX6F8DR4JVBZ2EMAGW62/DdKPt2MypMNQHAEwJ1qnVj3SCVELYM5cJ2NUU85vHxiEfQm9/01JM38NX768YTP15RW7C6ZCEZM#S5517
Excerpt from the log showing the failure:
thread 'app::sagas::snapshot_create::test::test_action_failure_can_unwind_no_pantry' panicked at nexus/src/app/sagas/test_helpers.rs:382:19:
instance 220fa211-507a-44df-952a-94c592ff0a5f did not transition to no_VMM after 120s: timed out after 120.641741736s
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 nexus/src/app/sagas/test_helpers.rs:382 and the app::sagas::snapshot_create::test::test_action_failure_can_unwind_no_pantry failure shown in the linked CI logs. Investigate why the instance does not transition to no_VMM within 120 seconds, then verify the resulting fix or diagnosis against the failing CI test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100