-
-
Notifications
You must be signed in to change notification settings - Fork 60
PR failure reporter has stopped working #548
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
Comments
I didn't find anything relevant in Twisted logs. For example, |
cc @pablogsal @zware |
Yeah these two PRs should have triggered and I just confirmed that those builders are in this list: buildmaster-config/master/master.cfg Line 288 in d5e7bc5
So not sure what is going on :( |
I am adding more logging for now #549 |
We need to wait until it fails again to investigate why is not happening I am afaid |
I looked today into why there was no comment for https://buildbot.python.org/all/#/builders/1594/builds/600. Seems the build id for this is: 1701133. You can check it using the API: https://buildbot.python.org/api/v2/builds/1701133 Checking the logs:
but there is no other trace |
So looks like
|
There is a lot of this:
but that happens all the time and looks unrelated. An looks like is for fetching an avatar??? ( |
Ah I found the problem. Turns out upstream changed how auth is passed down to the service in commit buildbot/buildbot@6b75ddf I will create a fix |
I think this is fixed will reopen if we keep having the problem |
It works again: python/cpython#127086 (comment) :-) (the failure is unrelated to the change, but the reporter works as expected.) |
Nice 👌 |
If I understand the code correctly, it's supposed to post a comment on a PR if a stable builder fails, and there has been exactly one commit to the branch since the previous success.
The last such comment was around the end of September. Here are a couple of more recent failures which should have caused a comment but didn't:
The text was updated successfully, but these errors were encountered: