desktopui_MashLogin failing on tricky with "Devtools client not yet ready: timed out" |
|||||||
Issue descriptionFailure in Legoland appears as "ABORT: Job aborted unexpectedly." First failure: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?id=3224670 Report details: This report is automatically generated to track the following Failure: Test: desktopui_MashLogin. Suite: chrome-informational. Chrome Version: None. Build: tricky-tot-chrome-pfq-informational/R73-11395.0.0-b3224670. Reason: Job aborted unexpectedly. build artifacts: https://storage.cloud.google.com/?arg=chromeos-image-archive/tricky-tot-chrome-pfq-informational/R73-11395.0.0-b3224670. results log: http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/266740718-chromeos-test/chromeos4-row2-rack3-host14/debug/. status log: http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/266740718-chromeos-test/chromeos4-row2-rack3-host14/status.log. job link: http://cautotest-prod/afe/#tab_id=view_job&object_id=266740718. You may want to check the test history: https://stainless.corp.google.com/search?test=^desktopui\_MashLogin$&first_date=2018-11-15&last_date=2018-12-13&row=model&col=build&view=matrix You may also want to check the test retry dashboard in case this is a flakey test: https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=desktopui_MashLogin Snippets from client log: 05:05:51 INFO | Chrome with Mash started and loaded OOBE. 05:05:51 DEBUG| Running 'screenshot "/tmp/screenshot.png"' 05:05:51 DEBUG| 'screenshot "/tmp/screenshot.png"' 05:05:51 WARNI| Unable to capture screenshot. Command <screenshot "/tmp/screenshot.png"> failed, rc=1, Command returned non-zero exit status * Command: screenshot "/tmp/screenshot.png" Exit status: 1 Duration: 0.0597500801086 stderr: [1213/050551.112623:ERROR:main.cc(100)] CRTC not found. Is the screen on?
,
Dec 13
Sigh. Stainless results from successful runs do not include the client log, so I can not tell if the 'Unable to capture screenshot' warning is normal (I suspect it is).
,
Dec 13
tricky is a Chromebox, so I think it's normal for us to not be able to take screenshots there. I don't have any idea about the "Devtools client not yet ready" error, though. Presumably that's from Telemetry.
,
Dec 13
I believe that "Devtools client not yet ready" is a generic "Chrome is unresponsive". eve has failed twice with this symptom also, and appears to have chrome crashes. Looking at the results now: https://stainless.corp.google.com/browse/chromeos-autotest-results/266744933-chromeos-test/
,
Dec 13
+xiyuan re: screenshots in tests.
,
Dec 13
Think screenshot error is a warning [1] and should not fail the test. It only fails the test if screenshot is captured and fails the color count sanity check. [1] https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/desktopui_MashLogin/desktopui_MashLogin.py?rcl=e3e6bc1eaaa104921bb78eec4be1e29d56c70e40&l=29
,
Dec 13
The client log: https://storage.cloud.google.com/chromeos-autotest-results/266740718-chromeos-test/chromeos4-row2-rack3-host14/debug/client.0.log It looks like there's a flaky chrome issue where chrome is non-responsive.
,
Dec 13
,
Dec 13
Actually, this is likely a mash bug, sorry
,
Dec 13
Not sure whether they are related we fail on eve board too, with more logs. But I have not dig out why yet. https://stainless.corp.google.com/browse/chromeos-autotest-results/266744933-chromeos-test/chromeos6-row4-rack12-host6/debug/
,
Dec 14
Yeah. In one of the eve failure, there appears to be a chrome crash in gpu::GpuChannelHost::Send, and a cros_camera_service crash in CameraMojoChannelManagerImpl::TearDownMojoEnv, but it's not in the other one, so it might be a red herring.
,
Dec 17
This stopped happening, presumably it was related to an issue tracked elsewhere and fixed. I will keep an eye on these builders however. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by steve...@google.com
, Dec 13