Successful tests registered as aborts |
||
Issue descriptionSuspecting a TKO issue Suite 1: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=77617281 09/22 15:40:48.402 INFO | server_job:0153| START ---- peppy-paladin/R55-8827.0.0-rc1/bvt-cq/hardware_Memtester.quick timestamp=1474584048 localtime=Sep 22 15:40:48 09/22 15:40:48.402 INFO | server_job:0153| ABORT ---- peppy-paladin/R55-8827.0.0-rc1/bvt-cq/hardware_Memtester.quick timestamp=1474584048 localtime=Sep 22 15:40:48 09/22 15:40:48.403 INFO | server_job:0153| END ABORT ---- peppy-paladin/R55-8827.0.0-rc1/bvt-cq/hardware_Memtester.quick timestamp=1474584048 localtime=Sep 22 15:40:48 Test 1: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=77617349 START ---- ---- timestamp=1474583924 localtime=Sep 22 15:38:44 START hardware_Memtester.quick hardware_Memtester.quick timestamp=1474583924 localtime=Sep 22 15:38:44 GOOD hardware_Memtester.quick hardware_Memtester.quick timestamp=1474583932 localtime=Sep 22 15:38:52 completed successfully END GOOD hardware_Memtester.quick hardware_Memtester.quick timestamp=1474583932 localtime=Sep 22 15:38:52 END GOOD ---- ---- timestamp=1474583933 localtime=Sep 22 15:38:53 Suite 2: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=77617213 09/22 15:41:45.877 INFO | server_job:0153| START ---- x86-alex-paladin/R55-8827.0.0-rc1/bvt-cq/platform_CheckPowerdProcesses timestamp=1474584105 localtime=Sep 22 15:41:45 09/22 15:41:45.878 INFO | server_job:0153| ABORT ---- x86-alex-paladin/R55-8827.0.0-rc1/bvt-cq/platform_CheckPowerdProcesses timestamp=1474584105 localtime=Sep 22 15:41:45 09/22 15:41:45.879 INFO | server_job:0153| END ABORT ---- x86-alex-paladin/R55-8827.0.0-rc1/bvt-cq/platform_CheckPowerdProcesses timestamp=1474584105 localtime=Sep 22 15:41:45 Test2: START ---- ---- timestamp=1474583981 localtime=Sep 22 15:39:41 START platform_CheckCriticalProcesses platform_CheckCriticalProcesses timestamp=1474583981 localtime=Sep 22 15:39:41 GOOD platform_CheckCriticalProcesses platform_CheckCriticalProcesses timestamp=1474583985 localtime=Sep 22 15:39:45 completed successfully END GOOD platform_CheckCriticalProcesses platform_CheckCriticalProcesses timestamp=1474583985 localtime=Sep 22 15:39:45 END GOOD ---- ---- timestamp=1474583987 localtime=Sep 22 15:39:47 Really strange. Both tests lack the TKO green bar on their job page.
,
Sep 22 2016
From the log, it seems that there was an exception between line 271 and 301. https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/tko/parse.py For troubleshooting purpose, we need a try-except around the call and log failures before exiting.
,
Sep 22 2016
Adding logging.
,
Oct 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/59ca5ac7437c7a1a253bb83d1fe7a300c8e6d273 commit 59ca5ac7437c7a1a253bb83d1fe7a300c8e6d273 Author: Simran Basi <sbasi@google.com> Date: Thu Sep 22 23:57:56 2016 autotest: log tko errors better BUG= chromium:649535 TEST=None Change-Id: I57574b032ee016564bdf1740a0661cd3a3878272 Reviewed-on: https://chromium-review.googlesource.com/388753 Commit-Ready: Dan Shi <dshi@google.com> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/59ca5ac7437c7a1a253bb83d1fe7a300c8e6d273/tko/parse.py
,
Aug 3
|
||
►
Sign in to add a comment |
||
Comment 1 by sbasi@chromium.org
, Sep 22 2016