Reduce Miri CI runtime by ignoring tests over 60 seconds
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 1.3k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 167
Description
### Is your feature request related to a problem or challenge?
Follow-up to #10803. The latest Miri run on main took 24m and reported 19 tests exceeding nextest’s 60-second slow-test threshold.
### Describe the solution you'd like
Mark those tests with #[cfg_attr(miri, ignore)] while preserving their normal cargo test coverage.
### Describe alternatives you've considered
_No response_
### Additional context
see https://github.com/apache/arrow-rs/pull/10803#issuecomment-5463002763 for more context
Contributor guide
Research direction
Review the context from #10803 and its linked pull-request comment, then run the Miri tests with nextest to identify the 19 tests exceeding the 60-second threshold. Add #[cfg_attr(miri, ignore)] to those tests while preserving normal cargo test coverage; done means the Miri run no longer reports those slow tests and regular tests still run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100