-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Auto-toolstate management follow-up. #48405
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
(I'll r? someone when it is ready.) |
46460a2
to
6125977
Compare
@bors try |
⌛ Trying commit 61259774b2eca687746973bee281d8fd4466144d with merge 89f74e21317085c7fa9e15c87bc308065b9cd358... |
Tested on commit rust-lang/rust@89f74e2. Direct link to PR: <rust-lang/rust#48405> 🎉 book on linux: test-fail → test-pass. 🎉 nomicon on linux: test-fail → test-pass. 🎉 reference on linux: test-fail → test-pass. 🎉 rust-by-example on linux: test-fail → test-pass.
☀️ Test successful - status-travis |
b0e29d0
to
b98561b
Compare
The *.md at the root directory in src/doc are no longer tested, but this should be fine since all files there are deprecated.
08590c0
to
ddc16dd
Compare
ddc16dd
to
b0f4e93
Compare
r? @Mark-Simulacrum or @alexcrichton cc @nrc — The comment will look like #48405 (comment). Also cc @rust-lang/docs. This PR affects the doc tests of the 4 external books (Nomicon, Reference, Rust-by-Example and The Book). After this PR,
|
@@ -59,6 +77,11 @@ if [ "$RUST_RELEASE_CHANNEL" = nightly -a -n "${TOOLSTATE_REPO_ACCESS_TOKEN+is_s | |||
sed -i "1 a\\ | |||
$COMMIT\t$(cat "$TOOLSTATE_FILE") | |||
" "history/$OS.tsv" | |||
# if we are at the last week in the 6-week release cycle, reject any kind of regression. | |||
if [ $SIX_WEEK_CYCLE -eq 5 ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be a lot more comfortable if this was a 4, since the 5 basically doesn't help much -- last release, we landed breakage to RLS on Monday of the 2nd to last week, which as far as I can tell, this wouldn't have caught. I would like the tools to ideally be green the week of the release, and the week before the release. That seems like a fairly reasonable requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is 1/3 rd of the release cycle, which seems kind of long. I think what is important is for tool authors to know if their tool is broken going into that final week, since they probably don;t keep track of the release cycle.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with leaving it at 5 for a cycle or two and then reevaluating if necessary; my hope is that over time there will be some other solution that we come up with...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about T-10 days as a compromise? 🤔
r=me pending updates to reviewers, I think |
b0f4e93
to
a9f940e
Compare
@bors r=Mark-Simulacrum Since there are no more comments on #48405 (review), I assume the reviewer list is good enough. |
📌 Commit a9f940e has been approved by |
🌲 The tree is currently closed for pull requests below priority 100, this pull request will be tested once the tree is reopened |
@bors p=1 (Reordered to prevent the rolled-up 48266 from being tested immediately after the rollup 48608. Also this PR should improve the CI time a bit.) |
…crum Auto-toolstate management follow-up. Tracking comment: #45861 (comment) * Fixed rust-lang-nursery/rust-toolstate#1, a proper link to the PR will be included. * Fixed rust-lang-nursery/rust-toolstate#2, a comment will be posted to the PR if the toolstate changed * Toolstate regression will be rejected at the last week of the 6-week cycle (currently entirely date-based). * Implemented https://internals.rust-lang.org/t/the-current-submodule-setup-is-not-tenable/6593, moved doc tests of Nomicon, Reference, Rust-by-Example and The Book to the "tools" job and thus allowed to fail like other external tools.
💔 Test failed - status-appveyor |
@bors retry p=0 3 hour timeout in |
…Mark-Simulacrum Auto-toolstate management follow-up. Tracking comment: rust-lang#45861 (comment) * Fixed rust-lang-nursery/rust-toolstate#1, a proper link to the PR will be included. * Fixed rust-lang-nursery/rust-toolstate#2, a comment will be posted to the PR if the toolstate changed * Toolstate regression will be rejected at the last week of the 6-week cycle (currently entirely date-based). * Implemented https://internals.rust-lang.org/t/the-current-submodule-setup-is-not-tenable/6593, moved doc tests of Nomicon, Reference, Rust-by-Example and The Book to the "tools" job and thus allowed to fail like other external tools.
Tracking comment: #45861 (comment)