CI log is sparse and does not give any clue to debug |
|||
Issue descriptionhttps://chromium-review.googlesource.com/c/chromium/src/+/1124201 failed with: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/cast_shell_linux/87450 I think the log is: https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8941773466961015168%2F%2B%2Fsteps%2Fcast_shell_browsertests__retry_summary_%2F0%2Fstdout step returned non-zero exit code: 1 Failure reason: 1 out of 1 aggregated steps failed. Failures: Step('cast_shell_browsertests (retry summary)') failed with return_code 1 This is not enough to understand what is going on.
,
Jul 6
looking a bit more, maybe cast_shell_browsertests (without patch) and cast_shell_browsertests (retry summary) should be given more proximity, and if there's a diff of two that would be more helpful to understand what is going on.
,
Jul 23
Moving to CCI, please pass to Infra>Platform if this should be handled at a lower level.
,
Jul 23
Any step with the text "(retry summary)" in its name isn't going to contain any useful debugging information. It just prints the list of individual tests that failed with your patch applied and subsequently succeeded without the patch applied. Since that list is nonempty in the given build, you'll want to find the test that failed with the patch applied. In this case that would be the step "cast_shell_browsertests (with patch)". Its log would be: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8941773466961015168/+/steps/cast_shell_browsertests__with_patch_/0/stdout Unfortunately, it seems bug 795156 has eaten that log, so we can no longer see how it failed. I suspect it would have looked like: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8940181849667868080/+/steps/cast_shell_browsertests__with_patch_/0/stdout Which should be enough to debug any failures you come across, so closing this out. Feel free to reopen if I missed something. |
|||
►
Sign in to add a comment |
|||
Comment 1 by uekawa@google.com
, Jul 6