New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 897782 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Oct 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 897869



Sign in to add a comment

[Chameleon: Eve/Coral/Fizz/Pyro] Audio and HDMI tests are failing with "Failed to start Chrome on DUT. Check multimedia_xmlrpc_server.log in result folder." on M72

Project Member Reported by sontis@chromium.org, Oct 22

Issue description

ChromeOS version: R72-11175.0.0

Duts: EVE, Coral,Pyro and Fizz

Failure reason: "Failed to start Chrome on DUT. Check multimedia_xmlrpc_server.log in result folder."


https://screenshot.googleplex.com/xe4rvOZZydH

logs:https://stainless.corp.google.com/browse/chromeos-autotest-results/250711833-chromeos-test/



From debug logs:
==============================================
10/21 23:45:35.552 DEBUG|        dev_server:0785| Check health for http://100.108.133.195:8082
10/21 23:45:35.910 DEBUG|        dev_server:0790| Pick http://100.108.133.195:8082
10/21 23:45:36.404 DEBUG|        dev_server:2758| CPU load of devserver http://100.109.175.145:8082 is at 91.4%, which is higher than the threshold of 80.0%
10/21 23:45:36.404 DEBUG|        dev_server:2758| CPU load of devserver http://100.109.169.114:8082 is at 98.4%, which is higher than the threshold of 80.0%
10/21 23:45:36.404 DEBUG|        dev_server:2758| CPU load of devserver http://100.109.169.115:8082 is at 98.4%, which is higher than the threshold of 80.0%
10/21 23:45:36.405 DEBUG|        dev_server:2758| CPU load of devserver http://100.108.133.199:8082 is at 87.7%, which is higher than the threshold of 80.0%
10/21 23:45:36.405 DEBUG|        dev_server:2758| CPU load of devserver http://100.108.133.196:8082 is at 100.0%, which is higher than the threshold of 80.0%
10/21 23:45:36.405 ERROR|        dev_server:2856| No devserver has the capacity to be selected.
10/21 23:45:36.405 INFO | site_crashcollect:0128| Failed to generate stack trace on devserver for dump /usr/local/autotest/results/lxc_job_folder/sysinfo/var/spool/crash/attestationd.20181021.234037.3736.dmp:
DevServerException('No crash server has the capacity to symbolicate the dump.',)
10/21 23:45:36.405 WARNI| site_crashcollect:0132| Failed to generate stack trace for /usr/local/autotest/results/lxc_job_folder/sysinfo/var/spool/crash/attestationd.20181021.234037.3736.dmp (see info logs)
10/21 23:45:36.406 INFO |        server_job:0217| INFO	----	----	timestamp=1540190736	localtime=Oct 21 23:45:36	Start crashcollection record
10/21 23:45:36.406 INFO |        server_job:0217| INFO	----	New Crash Dump	timestamp=1540190736	localtime=Oct 21 23:45:36	/usr/local/autotest/results/lxc_job_folder/crashinfo.chromeos15-row13a-rack4-host3/attestationd.20181021.234208.4732.dmp
===================================================================


Noticed lot of attestationd and tpm_managerd crashes.


AIs:
 1. Manually confirm chrome is working on ToT.






 
Blockedon: 897869
Able to reproduce this issue manually.
Not able to sign in to the device.
Components: -UI
Tests were running for these boards since few days back.  Issue 897541  had some fix updates.
Please check if this is still the case.
Status: Verified (was: Untriaged)
Tests are running on these boards now.
Screenshot: https://screenshot.googleplex.com/mUrWmK2zGhp

Able to recover nocturne successfully with build version 11196.0.0/72.0.3592.0 (which was blocked on  https://crbug.com/897782 )

Closing as verified.

Sign in to add a comment