Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 187993 Autotest client terminated unexpectedly DUT rebooted during the test run
Starred by 2 users Project Member Reported by ihf@chromium.org, Mar 12 2013 Back to list
Status: Duplicate
Merged: issue 217750
Owner: dshi@chromium.org
Closed: Apr 2013
OS: Chrome
Pri: 1
Type: Bug


Sign in to add a comment
OS: stout-release/R27-3814.0.0

We have seen two failures so far, the first happening R27-3814. The error message is: 

experimental_desktopui_VideoSanity                                                 ABORT: Autotest client terminated unexpectedly 
    DUT rebooted during the test run

The logs from the second failure can be found here
http://cautotest/tko/retrieve_logs.cgi?job=/results/2186825-chromeos-test/chromeos1-rack7-host2/debug/

I can't find evidence of a reboot in the log files though.
 
Comment 2 by tbroch@chromium.org, Mar 18 2013
Another instance of this failing @:
http://chromegw/i/chromeos/builders/stout%20canary/builds/1079
Comment 3 by scottz@chromium.org, Mar 18 2013
Owner: dshi@chromium.org
Status: Assigned
Routing to Dan to look at the run_suite error code. 

We should be ignoring all failures, regardless of the stage when the failure happens, if the test is experimental. 



Comment 4 by scottz@chromium.org, Mar 18 2013
Dan, please help ihf diagnose what is going on here and as a second part, look in to stopping run_suite.py from erroring when any experimental tests fail.
Comment 5 by dshi@chromium.org, Mar 18 2013
It seems that there were crashes during the test:

http://atlantis4.mtv.corp.google.com/results/2186825-chromeos-test/chromeos1-rack7-host2/crashinfo.chromeos1-rack7-host2/
in file kernel.20130312.130047.0.kcrash:
<2>[ 2633.015612] kernel BUG at /mnt/host/source/src/third_party/kernel/files/drivers/gpu/drm/drm_irq.c:930!

Same thing fir the occurrence in the first post:
http://atlantis4.mtv.corp.google.com/results/2247380-chromeos-test/chromeos1-rack7-host2/crashinfo.chromeos1-rack7-host2/

Note that the same crash happened in the same DUT, could that be some hardware failure?


Summary: [stout/zgb] experimental_desktopui_VideoSanity - Autotest client terminated unexpectedly DUT rebooted during the test run (was: [stout] experimental_desktopui_VideoSanity - Autotest client terminated unexpectedly DUT rebooted during the test run)
http://atlantis2.mtv.corp.google.com/results/2425186-chromeos-test/hostless/

Now also on ZGB
Labels: -Cr-Content-Video Cr-OS-Kernel-Video
ZGB HW has some media issue. On Stout, this should be fixed as per crosbug.com/p/18231. I will looks into this.
Project Member Comment 8 by bugdroid1@chromium.org, Apr 3 2013
Project: chromiumos/third_party/autotest
Branch : master
Author : Dylan Reid <dgreid@chromium.org>
Commit : 4f269c0fafa59d6fe80bc3a5898e1a80ed5a88b6

Code Review +2: Elly Jones
Verified    +1: Dylan Reid
Change-Id     : I0d4fc0d7989af384f4cd653b87def7bed1cc3bab
Reviewed-at   : https://gerrit.chromium.org/gerrit/47242

autotest: Disable desktop_VideoSanity in BVT

Re land this change as the test is still failing, now on more boards
than just stout.

see gerrit change 46138:

This test fails with a kernel crash on Stout, which in turn causes
Autotest to fail the Canary build rather than ignoring the result
because of the experimental label.  There is a already a tracking high
priority bug to fix this error, and the TPMs are fine with releasing
canaries with this bug on Stout.

BUG=chromium:187993
TEST=none, this removes a test.

Commit-Queue: Dylan Reid <dgreid@chromium.org>

D  client/site_tests/desktopui_VideoSanity/control.bvt
Cc: posciak@chromium.org taysom@chromium.org marc...@chromium.org
Labels: -Pri-2 -M-27 Pri-1 M-28
The video played fine when I ran it on the lab Stout devices. I don't see any kernel crash. 

Adding video and kernel team for investigation.
Status: Fixed
Didn't find any issue while running the test on two Stout machines. 
We are tracking the ZGB issue in Issue 219647.

https://gerrit.chromium.org/gerrit/#/c/47776/
Comment 11 by dshi@chromium.org, Apr 10 2013
I'd like to re-open this to follow up on following comment from scottz:

"...look at the run_suite error code. 

We should be ignoring all failures, regardless of the stage when the failure happens, if the test is experimental. "
Cc: -posciak@chromium.org -charliemooney@chromium.org -taysom@chromium.org -marc...@chromium.org
Labels: -Cr-OS-Kernel-Video Test-Support
Status: Assigned
Summary: Autotest client terminated unexpectedly DUT rebooted during the test run (was: [stout/zgb] experimental_desktopui_VideoSanity - Autotest client terminated unexpectedly DUT rebooted during the test run)
Since this is a test infra side fix, removing video/kernel team.
Comment 13 by beeps@chromium.org, Apr 10 2013
Just so I don't end up duping something thats a real issue, the unexpected reboot looks like a bug. #10 seems to indicate that it doesn't repro anymore. 

@#1: The line "DUT rebooted during the test run" is only printed out when the bootid changes, you will rarely find logged evidence of an unexpected reboot elsewhere ..unless it was a crash; #5 seems to indicate there were crashes. 

@#11: The issue of an experimental test closing the tree is tracked in 217750.
Comment 14 by dshi@chromium.org, Apr 11 2013
Mergedinto: 217750
Status: Duplicate
Sign in to add a comment