-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Disable broken targets #1593
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 broken targets #1593
Conversation
@gnzlbg: no appropriate reviewer found, use r? to override |
@bors: r+ |
1 similar comment
@bors: r+ |
r? me |
@bors: +r |
@bors are you still there? |
It's broken, you should call infra. |
@pietroalbini I see that GA is already active. Maybe that messed up bors somehow ? AFAICT rust-central-station is still using Azure, which is still correct. |
Can you retry any i686 windows-gnu build before disabling it? |
Still broken, thanks for testing. |
I'll take a look tomorrow. |
@bors: +r r+ |
@bors: r+ |
Let me investigate. @gnzlbg can you delegate me for this PR? It should be |
@bors delegate=pietroalbini |
@bors r=gnzlbg |
📌 Commit 0910f3b has been approved by |
@gnzlbg hmm, now it seems to be unstuck, but synchronization added failed PRs to the queue. Can you |
@bors: r+ |
📌 Commit 0910f3b has been approved by |
@pietroalbini looks like its working now |
What did you do to "unstuck" bors ? |
@gnzlbg I hit the "synchronize" button in the queue page. That button flushes all the cache bors has about a repo, forcing it to scrape all the open PRs again. It usually solves most of the problems, but it's a bit buggy (as you saw with the failed PRs being queued again). It should be used as a last resort, and it's usually best to ping us before hitting it. |
Thanks for fixing this! |
💔 Test failed - status-azure |
@bors: +r |
@bors: retry |
☀️ Test successful - checks-cirrus-freebsd-10, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, status-azure |
No description provided.