test aborted for unclear reason |
||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/wolf-paladin/builds/12390/steps/HWTest%20%5Bbvt-inline%5D/logs/stdio 10-11-2016 [12:25:28] Created suite job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=80359894 @@@STEP_LINK@Link to suite@http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=80359894@@@ The suite job has another 0:59:47.123192 till timeout. Suite timings: Downloads started at 2016-10-11 12:25:14 Payload downloads ended at 2016-10-11 12:25:25 Suite started at 2016-10-11 12:25:53 Artifact downloads ended (at latest) at 2016-10-11 12:25:57 Testing started at 2016-10-11 12:34:57 Testing ended at 2016-10-11 13:09:33 So we shouldn't have tined out from swarming. Suite job [ PASSED ] provision_AutoUpdate.double [ FAILED ] provision_AutoUpdate.double ABORT: Timed out, did not run. from https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/80359894-chromeos-test/hostless/debug/ 10/11 12:26:00.293 DEBUG| suite:0825| Scheduling provision_AutoUpdate.double 10/11 12:26:00.755 DEBUG| suite:1079| Adding job keyval for provision_AutoUpdate.double=80359987-chromeos-test and looking at that test results, it looks like it just died: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/80359987-chromeos-test/chromeos4-row1-rack4-host5/
,
Oct 21 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by kevcheng@chromium.org
, Oct 17 2016Status: Assigned (was: Untriaged)