Tracking Issue for spurious mingw CI failures
Open
Nobody has claimed this yet.
A-CI
C-tracking-issue
CI-spurious-fail-mingw
O-windows-gnu
T-bootstrap
T-compiler
T-infra
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
The spurious mingw failures might be related to #127883, but for the purpose of tracking, we should delineate the two general categories separately to avoid conflating them.
Please feel free to update specific classifications of kinds of spurious mingw failures.
Known problems
Misc
Label: https://github.com/rust-lang/rust/labels/CI-spurious-fail-mingw
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 by reading issues #127883 and #108227, then review the CI-spurious-fail-mingw label and the existing classifications in this tracking issue. Done means documenting or updating categories for spurious mingw failures while keeping them distinct from the failures tracked by #127883.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100