oxidecomputer / oxidecomputer/crucible
`test-crudd-benchmark` falsely reports success in CI
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
despite a Panic! In the test-crudd-benchmark, CI reports this as passing.
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 the linked Buildomat output for test-crudd-benchmark and the referenced pull request check to compare the panic with the reported CI status. Trace how this benchmark result is collected and classified; done means a panic causes CI to report failure rather than success, with coverage for the regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100