Skip to content

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

Merged
merged 6 commits into from
Mar 2, 2018

Conversation

kennytm
Copy link
Member

@kennytm kennytm commented Feb 21, 2018

Tracking comment: #45861 (comment)

@kennytm kennytm added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Feb 21, 2018
@rust-highfive
Copy link
Contributor

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 21, 2018
@kennytm kennytm removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 21, 2018
@kennytm
Copy link
Member Author

kennytm commented Feb 21, 2018

(I'll r? someone when it is ready.)

kennytm added a commit to rust-lang-nursery/rust-toolstate that referenced this pull request Feb 22, 2018
@kennytm kennytm force-pushed the autotoolstate-follow-up branch from 46460a2 to 6125977 Compare February 22, 2018 19:31
@kennytm
Copy link
Member Author

kennytm commented Feb 22, 2018

@bors try

@bors
Copy link
Collaborator

bors commented Feb 22, 2018

⌛ Trying commit 61259774b2eca687746973bee281d8fd4466144d with merge 89f74e21317085c7fa9e15c87bc308065b9cd358...

@kennytm-githubbot
Copy link

📣 Toolstate changed by #48405!

Tested on commit 89f74e2.
Direct link to PR: #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.

kennytm-githubbot added a commit to rust-lang-nursery/rust-toolstate that referenced this pull request Feb 22, 2018
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.
@bors
Copy link
Collaborator

bors commented Feb 22, 2018

☀️ Test successful - status-travis
State: approved= try=True

@kennytm kennytm force-pushed the autotoolstate-follow-up branch 2 times, most recently from b0e29d0 to b98561b Compare February 22, 2018 21:38
@kennytm kennytm force-pushed the autotoolstate-follow-up branch 2 times, most recently from 08590c0 to ddc16dd Compare February 22, 2018 23:26
@kennytm kennytm changed the title [WIP] Auto-toolstate management follow-up. Auto-toolstate management follow-up. Feb 22, 2018
@kennytm kennytm force-pushed the autotoolstate-follow-up branch from ddc16dd to b0f4e93 Compare February 22, 2018 23:49
@kennytm kennytm added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Feb 22, 2018
@kennytm
Copy link
Member Author

kennytm commented Feb 22, 2018

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,

  • These 4 books will only be tested on 64-bit Linux and Windows (MSVC). This should be fine according to @steveklabnik.

  • If an example from these books failed, the PR will still be allowed to merge. A comment will be posted after merging to announce the breakage, and GitHub will notify the people who maintain that book.

@@ -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
Copy link
Member

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.

Copy link
Member

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.

Copy link
Member

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...

Copy link
Member Author

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? 🤔

@Mark-Simulacrum
Copy link
Member

r=me pending updates to reviewers, I think

@kennytm kennytm force-pushed the autotoolstate-follow-up branch from b0f4e93 to a9f940e Compare February 23, 2018 16:54
@kennytm
Copy link
Member Author

kennytm commented Feb 25, 2018

@bors r=Mark-Simulacrum

Since there are no more comments on #48405 (review), I assume the reviewer list is good enough.

@bors
Copy link
Collaborator

bors commented Feb 25, 2018

📌 Commit a9f940e has been approved by Mark-Simulacrum

@bors
Copy link
Collaborator

bors commented Feb 25, 2018

🌲 The tree is currently closed for pull requests below priority 100, this pull request will be tested once the tree is reopened

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 25, 2018
@kennytm
Copy link
Member Author

kennytm commented Feb 28, 2018

@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.)

@bors
Copy link
Collaborator

bors commented Feb 28, 2018

⌛ Testing commit a9f940e with merge ab1f09e...

bors added a commit that referenced this pull request Feb 28, 2018
…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.
@bors
Copy link
Collaborator

bors commented Feb 28, 2018

💔 Test failed - status-appveyor

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Feb 28, 2018
@kennytm
Copy link
Member Author

kennytm commented Feb 28, 2018

@bors retry p=0

3 hour timeout in check x86_64-pc-windows-msvc.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2018
Manishearth added a commit to Manishearth/rust that referenced this pull request Mar 1, 2018
…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.
@bors bors merged commit a9f940e into rust-lang:master Mar 2, 2018
@kennytm kennytm deleted the autotoolstate-follow-up branch March 2, 2018 09:06
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants