-
Notifications
You must be signed in to change notification settings - Fork 57
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
When pushing to an r+'d PR, bors does not update the labels #9
Comments
Just ran into this as well - it's very confusing, I had a PR marked as 'S-waiting-on-bors' for 6 days because I didn't know I needed to |
It seems it is set up in rust and cargo, see Lines 71 to 74 in 6ff2d7f
However libc does only relabel on approved and failed: Lines 159 to 164 in 6ff2d7f
In which repo was you experiencing this ? |
This was in rust-lang/rust. |
I can't understand why it didn't relabeled. Is there any log that could help ? |
Here's a recent example (more info on Zulip): rust-lang/rust#79000 (comment) I remember one earlier that didn't have complicated commands ( |
I looked in the logs for that timeframe and saw no error. |
Does bors even have code that is attempting to update the labels when an r+'d PR is pushed to? Setting labels seems to work fine for the cases that are actually implemented, after all. |
It should be this code: Lines 559 to 574 in 68db8f6
|
example: rust-lang/rust#100811 (comment) |
Its removed from the r+ queue now. The queue does not update in realtime apparently 🙃 |
When I push to a PR that was r+'d, bors immediately removes it from the queue (looking at https://buildbot2.rust-lang.org/homu/queue/rust). However, the label in the respective PR still says "waiting-on-bors". It should get updated as well.
The text was updated successfully, but these errors were encountered: