peppy-paladin: desktopui_ExitOnSupervisedUserCrash: Timed out waiting for condition: Session stopped. |
||
Issue description+ sheriffs@, another timeout HWtest failed the CQ. Is there a bug filed to track this already ? https://luci-milo.appspot.com/buildbot/chromeos/peppy-paladin/16137 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/135253572-chromeos-test/ 08/15 11:59:17.602 DEBUG| utils:0212| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/desktopui_ExitOnSupervisedUserCrash/sysinfo/iteration.1"' 08/15 11:59:17.610 DEBUG| test:0395| after_iteration_hooks completed 08/15 11:59:17.611 WARNI| test:0612| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 606, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 806, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 470, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/desktopui_ExitOnSupervisedUserCrash/desktopui_ExitOnSupervisedUserCrash.py", line 66, in run_once raise error.TestFail(actual_problem) TestFail: Timed out waiting for condition: Session stopped.
,
Aug 16 2017
likely bad CL: https://chromium-review.googlesource.com/c/613667
,
Aug 16 2017
https://chromium-review.googlesource.com/c/613667 is the bad CL. The peppy-paladin tryjob failed https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/paladin/builds/3571 Bad CL found, close this bug. |
||
►
Sign in to add a comment |
||
Comment 1 by nxia@chromium.org
, Aug 15 2017