Skip to content

add instructions for triaging ICE issues #773

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 13, 2024
Merged

add instructions for triaging ICE issues #773

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d11a8ac
add instructions for triaging ICE issues
lolbinarycat Oct 24, 2024
002a7ea
add more info about ICE triage
lolbinarycat Oct 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/release/issue-triaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,19 @@ To see a list of all labels, check out the "labels" page next to the search bar
[IRLO]: https://internals.rust-lang.org/
[Discord]: https://discord.gg/rust-lang

### ICE Triage
For [Issues that have both I-ICE and needs-triage](https://github.com/rust-lang/rust/issues?q=is%3Aissue%20state%3Aopen%20label%3AI-ICE%20label%3Aneeds-triage)
* Check that the issue is actually an ICE, and not more accuratly described with `I-crash` or `I-hang`.
* If it is an older (like latest stable) version of rust, ask for or check the latest nightly.
* Check for duplicates, but don't close as duplicate unless you're sure they represent the same underlying issue.
Prefer simply linking to the issue as possibly related/duplicate.
* If it does not have a reproduction, comment asking for one and add S-needs-repro. if there isn't one for around a month it should generally be closed.
* If the reproduction is not minimal, add `E-needs-mcve` or create a Minimal Complete and Verifible Example yourself.
* Add `A-*` labels based on the code that causes the issue (check backtraces!),
and the nature of the repro (eg. if the repro is a weird trait impl or the backtrace points to `rustc_trait_selection`, add `A-traits`)
* Add `T-*`, `WG-*`, `PG-*`, `F-*`, `requires-*`, and `regression-*` labels as appropriate.


## Further triaging

For issues that have been through the initial triaging step (that is, don't have the `needs-triage` label anymore), there are usually
Expand Down
Loading