-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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.
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
[auto-toolstate] Upload the toolstate result to an external git repository, and removes BuildExpectation #46554
[auto-toolstate] Upload the toolstate result to an external git repository, and removes BuildExpectation #46554
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
WIP —
|
b1e7095
to
601da1a
Compare
@bors try |
⌛ Trying commit 601da1abce3d0442597033873cf3f95f5c604168 with merge 3c298ceb67465e8c644db661e8702180add73731... |
☀️ Test successful - status-travis |
clippy is broken? 🤔 |
Jup, I'm fixing it :) |
You can update the submodule to clippy's master branch. It was just some whitespace changes in ui output |
@oli-obk OK thanks 😄 It is worrying that the CI did not catch this, so I've updated |
edf37eb
to
4913a4e
Compare
@bors try Second try:
|
⌛ Trying commit 4913a4e00e8eee49adb6fcbd2ec2de198bd4a19b with merge d215e0befefe6c0024072c3e5b94715872a55108... |
💔 Test failed - status-travis |
4913a4e
to
0316a5a
Compare
⌛ Trying commit 0316a5aea8da99d41e253188bb8b67d92465af73 with merge e7f03ae4e474aefeb8129bcda1deba52327b64b8... |
💔 Test failed - status-travis |
0316a5a
to
6e4a35c
Compare
⌛ Trying commit 6e4a35c96ff889557bec2db33bb8ec575e3244f1 with merge 13211b7c46993c26873b647f20df9952e33cd4e6... |
💔 Test failed - status-travis |
@oli-obk Just to let you know, clippy's dogfood test failed to run due to read-only file system.
Looks like rust/src/bootstrap/mk/Makefile.in Lines 53 to 65 in f4f1858
|
@bors r=alexcrichton |
📌 Commit c9d3303 has been approved by |
⌛ Testing commit c9d330303df7d8dedb2e9103c9e0c0ee52cea614 with merge cf104e543b15d200679f6a6a88a7938656d1c3e9... |
💔 Test failed - status-appveyor |
This reverts commit ab018c7. This also adds the `ToolBuild::is_ext_tool` field to replace the previous `ToolBuild::expectation` field, to indicate whether a build-failure of certain tool is essential.
c9d3303
to
44954ab
Compare
@bors r=alexcrichton |
📌 Commit 44954ab has been approved by |
…and-remove-toolstate-toml, r=alexcrichton [auto-toolstate] Upload the toolstate result to an external git repository, and removes BuildExpectation This PR consists of 3 commits. 1. (Steps 4–6) The `toolstate.json` output previously collected is now pushed to the https://github.com/rust-lang-nursery/rust-toolstate repository. 2. (Step 7) Revert commit ab018c7, thus removing all traces of `BuildExpectation` and `toolstate.toml`. 3. (Step 8) Adjust CONTRIBUTION.md for the new procedure. These are the last steps of #45861. After this PR, the toolstate will be automatically computed and published to https://rust-lang-nursery.github.io/rust-toolstate/. There is no need to manage toolstate.toml again. Closes #45861.
☀️ Test successful - status-appveyor, status-travis |
Tested on commit rust-lang/rust@503153e. 💔 rls on windows: test-fail → build-fail (cc @nrc). 💔 rls on linux: test-fail → build-fail (cc @nrc). 💔 rustfmt on windows: test-pass → build-fail (cc @nrc). 💔 rustfmt on linux: test-pass → build-fail (cc @nrc).
wooohoo! Thanks for the awesome work @kennytm |
[WIP] Requires tools to test-pass if the corresponding submodule is updated. Follow up of #46554. Breaking a tool would not stop bors from accepting a merge, but this also means when we intend to *fix* a tool but failed, bors will *still* accept the PR. This behavior is not helpful to the tool maintainers. This PR attempts to fix this by rejecting the tool-update merge when a tool failed. It recognizes a PR as "tool-updating" when the corresponding submodule is changed, compared with the previous commit. [WIP] - Final check to ensure the CI is interpreting the PR description correctly.
Requires tools to test-pass if the corresponding submodule is updated. Follow up of #46554. Breaking a tool would not stop bors from accepting a merge, but this also means when we intend to *fix* a tool but failed, bors will *still* accept the PR. This behavior is not helpful to the tool maintainers. This PR attempts to fix this by rejecting the tool-update merge when a tool failed. It recognizes a PR as "tool-updating" when the corresponding submodule is changed, compared with the previous commit.
This PR consists of 3 commits.
toolstate.json
output previously collected is now pushed to the https://github.com/rust-lang-nursery/rust-toolstate repository.BuildExpectation
andtoolstate.toml
.These are the last steps of #45861. After this PR, the toolstate will be automatically computed and published to https://rust-lang-nursery.github.io/rust-toolstate/. There is no need to manage toolstate.toml again.
Closes #45861.