from: https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_speedy-paladin/builds/1428/steps/HWTest%20%5Bbvt-cq%5D/logs/stdio
The logs say: video_VideoSanity.vp9 ABORT: Timed out, did not run.
but digging into it, we see that the job actually passed:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/57653423-chromeos-test/chromeos4-row4-rack10-host21/
The suite itself didn't time out:
Suite timings:
Downloads started at 2016-03-23 15:19:05
Payload downloads ended at 2016-03-23 15:19:10
Suite started at 2016-03-23 15:19:35
Artifact downloads ended (at latest) at 2016-03-23 15:19:36
Testing started at 2016-03-23 15:23:07
Testing ended at 2016-03-23 15:38:46
The test finished within 2 mins:
START ---- ---- timestamp=1458772432 localtime=Mar 23 15:33:52
START video_VideoSanity video_VideoSanity timestamp=1458772432 localtime=Mar 23 15:33:52
GOOD video_VideoSanity video_VideoSanity timestamp=1458772459 localtime=Mar 23 15:34:19 completed successfully
END GOOD video_VideoSanity video_VideoSanity timestamp=1458772459 localtime=Mar 23 15:34:19
END GOOD ---- ---- timestamp=1458772460 localtime=Mar 23 15:34:20
It looks like the parser never picked it up (the jobid-57653423 gets listed once at the top of .parse.log)
Possible bug in parser?
Comment 1 by kevcheng@chromium.org
, Mar 23 2016