CQ test failure information not being displayed |
|||
Issue descriptionI have a CL with a broken test, but trybots are not displaying any failure information. Instead, they just display "LogDog: <path>" at the top, with no further information. Signing in with either my chromium.org or google.com account does not fix this. Sample failure: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/454776 (Search for browser_tests - not the trigger at the top, and click on stdout or the line to the failing test). Not sure if the issue is the CQ, LogDog, or what. I've seen this same problem on a number of CLs, so not just a bad try run.
,
May 16 2017
And yet again I'm having this issue. I thought it might be because I was opening the links too soon after the failed try runs, but now opening some nearly a day after, and still getting a blank log.
,
May 16 2017
,
May 16 2017
,
May 16 2017
Are you using Chrome canary? There is a known issue w/ a Chrome 60+ that fails. If you can, pull up your JS console view and copy the contents. FWIW the log in #1 and #3 both load just fine for me on Chrome 58, so I cannot reproduce with the available information.
,
May 17 2017
It happened on both Canary and stable. I can't repro it now, but I run into it often enough that I expect I'll run into it again in the near future.
,
May 17 2017
Since neither of us can reproduce and I suspect that this is related to a different bug, I'm going to close for now as "WontFix". Please re-open with: - Chrome version - Contents of your JS console log ... if you observe this again, and we can try and figure out what's going on. |
|||
►
Sign in to add a comment |
|||
Comment 1 by mmenke@chromium.org
, May 15 2017