New issue
Advanced search Search tips

Issue 760376 link

Starred by 4 users
Status: Archived
Owner: ----
Closed: Sep 3
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

[Telemetry] Error while executing Telemetry benchmarks

 
Chrome OS Version: 62.0.3199.0 (Official Build)
Chrome OS Platform: 9889.0.0 dev-channel reef test
Firmware Version: Google_Reef.9042.87.1

Steps To Reproduce:
./run_benchmark --remote=<<ChromeOS Device IP>> --browser=cros-chrome smoothness.top_25_smooth. (other benchmarks gives the same error as well, such
as pagecycler. This is seen on Apollolake as well as Skylake platforms)

Expected Result:
Smoothness.top25 as well as other benchmarks that uses telemetry should be
successfully executed, with results stored in results.html.

Actual Result:
A timeout error.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

Please provide any additional information below. Attach a screen shot or
log if possible.

Error message after attempting to run benchmark on DUT:

(ERROR) 2017-08-29 04:14:45,356 browser.__init__:65  Failure while starting browser backend.
Traceback (most recent call last):
  File "/home/michael/ssd/chromiumos-2-pnp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 58, in __init__
    self._browser_backend.Start()
  File "/home/michael/ssd/chromiumos-2-pnp/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/home/michael/ssd/chromiumos-2-pnp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py", line 140, in Start
    self._WaitForBrowserToComeUp()
  File "/home/michael/ssd/chromiumos-2-pnp/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/home/michael/ssd/chromiumos-2-pnp/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/chrome_browser_backend.py", line 159, in _WaitForBrowserToComeUp
    raise exceptions.BrowserConnectionGoneException(self.browser, e)
BrowserConnectionGoneException: Timed out while waiting 240s for HasBrowserFinishedLaunching.
Found Minidump: False
Stack Trace:
********************************************************************************
	Cannot get stack trace on CrOS
********************************************************************************
Standard output:
********************************************************************************
	Cannot get standard output on CrOS
********************************************************************************
System log:
(Not implemented)
(WARNING) 2017-08-29 04:14:45,357 shared_page_state.DumpStateUponFailure:132  Cannot dump browser state: No browser.
(WARNING) 2017-08-29 04:14:45,357 shared_page_state.DumpStateUponFailure:140

Comment 1 by michael....@intel.corp-partner.google.com, Aug 30 2017 

Was not able to re-produce this issue on a R61 image.

Comment 2 by colex.ne...@intel.corp-partner.google.com, Aug 30 2017 

This is reproducible for R62-9877 and R62-9868 on two distinct, very recent ChromeOS platforms.  Happens for both smoothness and page_cycler. 

The telemetry server connects to the DUT, appears to try to log in as the test user (screen goes black except for the lower right UI panel).  Attached is the content of the ui.LATEST, which whines about certificates.
ui.LATEST
2.9 KB Download

Comment 3 by colex.ne...@intel.corp-partner.google.com, Aug 30 2017 

localhost ~ # cat /var/log/ui/ui.LATEST 
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva error: /usr/lib64/va/drivers/i965_drv_video.so init failed
libva info: va_openDriver() returns -1

DevTools listening on ws://127.0.0.1:41931/devtools/browser/8e01a72e-5566-45a5-b0a7-3d6aedfa80cc
  device-enumerator: scanning /sys/class
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[11923:11923:0830/081803.582839:ERROR:device_event_log_impl.cc(156)] [08:18:03.582] Network: network_state.cc:340 Invalid WebProxyAutoDiscoveryUrl: /service/0: "
"
[11923:11957:0830/081803.971054:ERROR:service_manager.cc(156)] Connection InterfaceProviderSpec prevented service: content_browser from binding interface: ash::mojom::TabletModeManager exposed by: ash
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[11923:11942:0830/081804.134296:ERROR:cert_verify_proc_nss.cc(921)] CERT_PKIXVerifyCert for play.google.com failed err=-8172
[11923:11991:0830/081804.619291:ERROR:cert_verify_proc_nss.cc(921)] CERT_PKIXVerifyCert for www.google.com failed err=-8172
[11923:11942:0830/081805.016837:ERROR:cert_verify_proc_nss.cc(921)] CERT_PKIXVerifyCert for www.gstatic.com failed err=-8172
[11923:11923:0830/081805.115166:ERROR:CONSOLE(9960)] "TypeError: Cannot read property 'addObserver' of null
    at HTMLDivElement.decorate (chrome://oobe/oobe.js:18792:20)
    at HTMLDivElement.initializeImpl_ (chrome://oobe/oobe.js:226:12)
    at HTMLDivElement.initialize (chrome://oobe/oobe.js:122:35)
    at Object.api.register (chrome://oobe/oobe.js:435:18)
    at Function.initialize (chrome://oobe/oobe.js:19469:32)
    at HTMLDocument.<anonymous> (chrome://oobe/oobe.js:9946:10)", source: chrome://oobe/oobe.js (9960)
[11923:11923:0830/081805.115239:ERROR:CONSOLE(18792)] "Uncaught TypeError: Cannot read property 'addObserver' of null", source: chrome://oobe/oobe.js (18792)
[11923:11991:0830/081813.516872:ERROR:cert_verify_proc_nss.cc(921)] CERT_PKIXVerifyCert for ssl.gstatic.com failed err=-8172
[11923:11923:0830/081859.118378:ERROR:device_event_log_impl.cc(156)] [08:18:59.118] Network: network_state.cc:340 Invalid WebProxyAutoDiscoveryUrl: /service/0: "
"
[11923:11923:0830/081859.320348:ERROR:device_event_log_impl.cc(156)] [08:18:59.320] Network: network_state.cc:340 Invalid WebProxyAutoDiscoveryUrl: /service/0: "
"
[11923:11923:0830/081859.341695:ERROR:device_event_log_impl.cc(156)] [08:18:59.341] Network: network_state.cc:340 Invalid WebProxyAutoDiscoveryUrl: /service/0: "

Comment 4 by zalcorn@chromium.org, Aug 31 2017

Components: Tests>Telemetry

Comment 5 by colex.ne...@intel.corp-partner.google.com, Aug 31 2017 

This is a result of a change in the browser API, has been patched in newer telemetry version.
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 3

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment