Skip to content
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

Log analysis message can be significantly delayed and show up after the next bors run is already going #79

Open
RalfJung opened this issue Nov 29, 2023 · 2 comments

Comments

@RalfJung
Copy link
Member

This message refers not to the bors run that started in the message just before, it refers to the run that failed here. That means the message was 30min delayed, and also the fact that there already was a new bors run means it was very confusing to still yet a log analysis message from the previous run.

@WaffleLapkin
Copy link
Member

I want to highlight that this happens all the time and is always very confusing

@RalfJung
Copy link
Member Author

RalfJung commented Apr 24, 2024

Just happened again in rust-lang/rust#104087 and confused @matthiaskrgr (and others). This message did not refer to the bors build that just started above, but then a bors retry was used which canceled a perfectly fine build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants