-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Disable validate_maintainers. #88977
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=101 I think most of the time the validation broke when users renamed themselves. Maybe the way to go is move the pinging/assignment out of the toolstate code and into e.g. triagebot, which has more options for who to yell at, and make it depend on rust-lang/team there (which validates users existence and fails CI). |
📌 Commit 6070763 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. |
⌛ Testing commit 6070763 with merge a011a3ec4c6f3351c473f094871fe8bc40d57daa... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors retry Not really clear why it failed. No failed jobs, just a few listed as "cancelled". |
⌛ Testing commit 6070763 with merge f2f9fe5bdafb84a9aebe13ae9741a2337737a132... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors retry I have no idea why this is failing. |
⌛ Testing commit 6070763 with merge 0c593eb4ae08b7a1599f40f6809d1246cc0f7812... |
⌛ Testing commit 6070763 with merge b42c69271cb5c234317c7da35b31556450952f0a... |
@Manishearth Oh, sorry, should have posted here, too. The error is legit, there was an image update this morning. I'm going to poke at it a bit. |
@bors r- |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
GitHub updated the Windows image this morning with a new WDK which brings about a new debugger version (10.0.22000.1) which has caused one of the debuginfo tests to fail. I disabled it for now to get CI moving. Image changes: actions/runner-images@adce9b6#diff-816219d3c9f30fcc1c40f88ca826c1662bf99eded781c1b419dd2dfb577ae227 @bors r=Mark-Simulacrum |
📌 Commit 66a1987 has been approved by |
☀️ Test successful - checks-actions |
Who needs to evaluate the beta nomination here? The issue is presumed to be blocking the current backports in #88946. |
beta-accepting unilaterally. |
[beta] backports - rustdoc: Fix ICE with `doc(hidden)` on tuple variant fields rust-lang#88639 - Fix 2021 `dyn` suggestion that used code as label rust-lang#88657 - Workaround blink/chromium grid layout limitation of 1000 rows rust-lang#88776 - Change scope of temporaries in match guards rust-lang#88678 - Add a regression test for rust-lang#88649 rust-lang#88691 - Revert anon union parsing rust-lang#88775 - Disable validate_maintainers. rust-lang#88977 Also drop stage0 rustfmt, because that's only supposed to be used on master. r? `@Mark-Simulacrum`
The validate_maintainers check has started to fail with the error:
Apparently GitHub has restricted the collaborators API to admins. For now, this just disables the check to get CI working again. Eventually, I think we'll just need to remove the check since we will unlikely use an admin token, and I don't see a workaround. The
MAINTAINERS
list doesn't change often, so we may just need to put a sternly worded comment near the list.