-
Notifications
You must be signed in to change notification settings - Fork 100
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
Unclear buildbot failure email #65
Comments
Thanks for following up on this! |
Looks like llvm-zorg does not parse logs well in the case of a build cancelled because of timeout. The relevant chunk of log:
The same issue is with the email notifier. That has a wrong summary, as well as the quoted chunk of log is not actually relevant to the issue. |
For the sake of completeness, here is the quoted log from email notification:
|
llvm#65 Listen to the `header` TTY stream and monitor the message like `command timed out: 1200 seconds without output running [b'ninja', b'check-clang-unit'], attempting to kill` send from a worker.
llvm#65 Listen to the `header` TTY stream and monitor the message like `command timed out: 1200 seconds without output running [b'ninja', b'check-clang-unit'], attempting to kill` sent from a worker.
#65 Listen to the `header` TTY stream and monitor the message like `command timed out: 1200 seconds without output running [b'ninja', b'check-clang-unit'], attempting to kill` sent from a worker.
This issue has been fixed. |
Reported by @jayfoad for an email from the rv64gc-qemu-user-single-stage bot (administered by me). The relevant build failure is this one.
Issues with the email:
As this bot doesn't have anything exotic in terms of its buildbot config (ref) I'd assume this is a generic buildbot/llvm-zorg issue, but of course would love to hear if there's anything I'm missing on my end.
As I noted in a separate email thread, the mooted "gatekeeper" bot support would be a huge help in avoiding builder runs that identify an issue not specific to that builder that's been fixed in the mean time. Though that wouldn't directly fix the fact the generated email was confusing in this case.
The text was updated successfully, but these errors were encountered: