You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
functions/tips: should call a GCP API failed #1758
This failure seems unrelated to the labeled commit. I suspect it's a flaky test.
More concerningly however, there are no test logs to be read (it seems like the "output test results to XML" functionality failed, or the logs were otherwise swallowed), so debugging this failure is essentially impossible.
@fhinkel what should we do here? Re-run the test and mark closed if it passes, or try to investigate why the failure occurred? (@tbpg it might help if the build-cop bot added a copy of the failure logs to the issue itself.)
Activity
ace-n commentedon Apr 29, 2020
This failure seems unrelated to the labeled commit. I suspect it's a flaky test.
More concerningly however, there are no test logs to be read (it seems like the "output test results to XML" functionality failed, or the logs were otherwise swallowed), so debugging this failure is essentially impossible.
@fhinkel what should we do here? Re-run the test and mark closed if it passes, or try to investigate why the failure occurred? (@tbpg it might help if the build-cop bot added a copy of the failure logs to the issue itself.)
flaky-bot commentedon Apr 30, 2020
Test passed for commit 774ee22 (Build Status, Sponge)! Closing this issue.
tbpg commentedon Apr 30, 2020
@ace-n that idea has come up a couple times -- I like it. Mind filing a feature request at https://github.com/googleapis/repo-automation-bots/issues/new/choose?
tbpg commentedon May 1, 2020
Closing the loop here, the bot will now include the failure log in comments. :) Thank you for the feature request!
Edit: now* include