oxidecomputer / oxidecomputer/omicron

test failed in CI: oximeter-collector agent::tests::test_self_stat_error_counter

Open
#10,503 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Test Flake
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

This test failed on a CI run on https://github.com/oxidecomputer/omicron/pull/10500:

https://github.com/oxidecomputer/omicron/pull/10500/checks?check_run_id=78342847644

Log showing the specific test failure:

https://buildomat.eng.oxide.computer/wg/0/details/01KSQR0FVX669WDC81SJZ98AA5/mccBgeWXWTJhk9RLWazrSDONQwOzMdAI6ljC2LYBMSZhSA53/01KSQR0XRSZVQ8QS7MABQ96CK0#S9079

Excerpt from the log showing the failure:

2026-05-28T17:23:27.462Z	    thread 'agent::tests::test_self_stat_error_counter' (2) panicked at oximeter/collector/src/agent.rs:1020:14:
2026-05-28T17:23:27.462Z	    called `Option::unwrap()` on a `None` value

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the CI log for agent::tests::test_self_stat_error_counter and the panic at oximeter/collector/src/agent.rs:1020. Trace the failing unwrap and inspect the surrounding test and implementation. Done means the test no longer panics and the CI check passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.