-
Notifications
You must be signed in to change notification settings - Fork 135
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
Build Cop: possible missing report #532
Comments
Thanks for the report. I'm looking into the logs now. |
I think I found the logs for this particular build. I don't know why the issue was not filed -- I don't see any errors. I'm going to add some additional logging to the bot to hopefully help next time this happens. |
cc @codyoss, who has also seen something like this. Please update this thread if you spot this again. |
Another instance: Build: Log:
My suspicion is that this test failed with somewhat long log output. The xml file is 485 KB. You can download it from the resultstore UI. |
The extra logging was helpful -- the failure was successfully parsed:
Unfortunately, there are no other logs indicating why the issue wasn't filed. |
Another one: d4152082-608d-425a-a5a7-0e6890562a19 |
Another one: fdf704c7-bc2b-40c4-8ff6-abc657cc6dec I see some log entries with that ID. But, I don't see an invocation with a failed test. The previous instances of this bug had logs that showed the failure was successfully parsed. That particular scenario should be fixed with the However, with this build, I don't see the failure at all. |
I checked the logs around that time and don't see any relevant errors. I also downloaded the XML file and confirmed it is successfully parsed. @orthros is there a way we could get the PubSub publish ID from the bot? When the logs are sent to PubSub, we have logs like this:
I'd like to log that ID from the bot so we can confirm the bot is actually seeing all of the PubSub messages. |
986af32d-f777-40b5-8fbc-bd7c467b912c is the exact same. That's another build for a different Go version from the same overall build. Notably, the test failures are from the largest sponge_log.xml files for both builds. Perhaps @tmatsuo's idea about the message being too large is correct? |
I'd have to do a bit more digging into the PubSub mechanism of this (I'm not terribly familiar with BuildCop) but it sounds like something that is possible. |
|
In an assumption that adding instances helps. Let me know if you don't need this any more. (build)[https://source.cloud.google.com/results/invocations/fe90a7a5-508a-46db-bc85-4f102c14bb96/targets/github%2Fpython-docs-samples%2Fvision%2Fautoml/tests] Log:
|
In the build, one of the failures is for directory
container_registry/container_analysis
.The log says:
However, we don't see an issue on the repo.
I think the previous issue is:
GoogleCloudPlatform/python-docs-samples#2894
but it was closed 15 days ago.
The text was updated successfully, but these errors were encountered: