Eagerly queue up failed builds from old rustdoc versions when rustdoc is updated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 233
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
coming from https://github.com/rust-lang/docs.rs/issues/301
Eagerly queue up failed builds from old rustdoc versions when rustdoc is updated, at a lower priority than user requests. For the same reason as before, this lets us try to eagerly rebuild crates that may have failed due to the old rustdoc, while not clogging up the queue for new releases.
now added by me:
I have the feeling (that needs data) that most of the build failures aren't related to rustdoc issues that are fixed with newer versions. This means the impact of this automation might be wasted build time.
Contributor guide
No contributing guide indexed for this repository
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 the linked docs.rs issue #301 and investigate how failed builds and rustdoc updates are currently queued. The payload names no files or tests; the work is done when a measured, agreed approach exists for retrying eligible old failures at lower priority without unnecessarily consuming build capacity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100