rust-lang / rust-lang/rust-clippy
empty_array.rs test removed because it ICEs on CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
In https://github.com/rust-lang/rust-clippy/pull/4606 I removed tests/ui/out_of_bounds_indexing/empty_array.rs because it was ICEing, but only on rustc CI (https://github.com/rust-lang/rust/pull/64963#issuecomment-537233469)
We should restore the test when we figure out what's going on here. I've got a full rustc build ongoing in the background for now.
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 tests/ui/out_of_bounds_indexing/empty_array.rs and the linked Clippy and rustc pull requests to understand the CI-only ICE. Reproduce it with the rustc build mentioned in the issue, then restore the test once the cause is understood and it no longer ICEs on rustc CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100