Issue metadata
Sign in to add a comment
|
Diagnosing webkit_layout_tests failures is very difficult |
||||||||||||||||||||||||
Issue descriptionTrying to diagnose this failure is quite difficult: https://ci.chromium.org/buildbot/tryserver.chromium.mac/mac_chromium_rel_ng/685960 This link says very little about what tests were run or what any of the output was: https://chromium-swarm.appspot.com/task?id=3ca61f6ac5d2c310&refresh=10&show_raw=1 If I click this link, Chrome slows to a crawl trying to load it. (Perhaps LogDog should just give up and let me download the raw file?) It's also far too large to extract anything useful out of. https://logs.chromium.org/v/?s=chromium%2Fbb%2Ftryserver.chromium.mac%2Fmac_chromium_rel_ng%2F685960%2F%2B%2Frecipes%2Fsteps%2Fwebkit_layout_tests_on_Intel_GPU_on_Mac__with_patch__on_Mac-10.12.6%2F0%2Fstdout I'm still at a loss as to what the failure was and am forced to just retry the CQ job hoping it won't time out the next time. What I would like to see is: - The output for *just* the failed shard. - What tests it was supposed to run. - What tests it managed to run and how long they took. - What test it was in the middle of running and how long it spent on it. The output appears to be in some sort of machine-readable JSON format, for the most part, but there the JSON is just provided for the human to read rather than consumed into some usable tool.
,
Apr 4 2018
Assigning to M-A because these sorts of changes are beyond just a simple UI tweak.
,
Apr 4 2018
Thanks for the comments. There's a few things in there. - The logs.chromium.org host is "logdog", which is a separate service. I'd recommend commenting on issue 809308 . - The task timed out during mapping, this is issue 794085 . :/
,
Apr 4 2018
Ah, I see. You mean it's timing out somewhere in the process of handling the sharding itself, rather than any particular test? Okay, in that case it's pretty understandable that I wasn't able to get useful information on which test(s) were slow. :-) |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by davidben@chromium.org
, Apr 3 2018