paritytech / paritytech/parity-common
[ci]: run Miri on all crates to detect potential undefined behavior
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 311
- Forks
- 245
- PR merge metrics
- No merged PRs in 30d
Description
Miri can help find undefined behavior in programs which would be helpful.
For example I tried it on parity-crypto and https://github.com/paritytech/parity-common/issues/472 was detected by Miri
However, Miri is platform-indepedent interpreter so it has no access to most platform-specific APIs or FFI. which makes it not possible to run on some dependencies and similar. Then those has to marked by #[cfg_attr(miri, ignore)] or something similar which is quite many tests unfortunately.
Thoughts?
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
No file or test entry point is named. Start by reviewing how the repository's crates and tests could be run under Miri, then identify dependencies using platform-specific APIs or FFI that need Miri-specific handling. Done means CI runs Miri across the feasible crates while the unsupported cases are explicitly handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100