Type of hardware  : hana PVT SKU4-1 (C107822)
Chrome OS Version : R64-10088.0.0
BIOS Version      : Google_Hana.8438.85.0 / Google_Hana.8438.111.0
EC Version        : hana_v1.1.4807-60186a1 / hana_v1.1.4811-ecfdf3a

CPU arch     : aarch64
CPU model    : ARMv8 Processor rev 2 (v8l)
CPU speed    : 1703.0000
Total Memory : 4033280 kB
Memory Type  : 1-45: SK Hynix (Hyundai) | 00000000 | H9CCNNNBJTALAR-NUD
MMC Model    : BJNB4R
MMC Firmware : 0x0700000000000000

Please specify Cr-* Power_LoadTest

Steps To Reproduce:
(1) Run power Load Test
see detailed instructions at 
https://testtracker.googleplex.com/efforts/testcase/detail/21021297?tp_id=382&result=&environment=

Expected Result:
Test should login and start run for 6-10 hours until battery is <=5%

Actual Result:

Test logged and immediately logged out


TART	power_LoadTest	power_LoadTest	timestamp=1509557197	localtime=Nov 01 10:26:37	
		FAIL	power_LoadTest	power_LoadTest	timestamp=1509557224	localtime=Nov 01 10:27:04	Unhandled DevtoolsTargetCrashException: Devtools target crashed
  ********************************************************************************
  (/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:492 _ConvertExceptionFromInspectorWebsocket) Original exception:
  [Errno 104] Connection reset by peer
  ********************************************************************************
  (/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:513 _AddDebuggingInformation) Received a socket error in the browser connection and the tab no longer exists. The tab probably crashed.
  ********************************************************************************
  (/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:514 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:39713/devtools/page/(66E50762F304B1A3319F621DFF7870D9)
  Found Minidump: False
  Stack Trace:
  ********************************************************************************
  	Cannot get stack trace on CrOS
  ********************************************************************************
  Standard output:
  ********************************************************************************
  	Cannot get standard output on CrOS
  ********************************************************************************
  System log:


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

Always.

What is the impact to the user, and is there a workaround? If so, what is
it?

test works with R64-10081.0.0.

Test also failing with R63: https://b.corp.google.com/issues/68641816



 

Deleted: power_LoadTest.tar.gz 398 KB

power_LoadTest.tar.gz 398 KB Download

Deleted: debug-logs_20171101-110308.tgz 116 KB

debug-logs_20171101-110308.tgz 116 KB Download