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

Issue 735258 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

system_health.memory_mobile failure on chromium.perf on Nexus 5

Project Member Reported by charliea@chromium.org, Jun 20 2017

Issue description

Link to failing step log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5_Perf%2F161%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile_on_Android%2F0%2Fstdout

This isn't a normal failure: it looks like it's a Telemetry/infra failure related to not being able to find some file. Where I'd expect to normally see on the luci page the list of failing stories, I'm instead seeing "TEST RESULTS WERE INVALID".

An excerpt from the logs is:

Additional test environment:
    CHROME_DEVEL_SANDBOX=/opt/chromium/chrome_sandbox
    LANG=en_US.UTF-8
Command: /usr/bin/python ../../testing/scripts/run_telemetry_benchmark_as_googletest.py ../../tools/perf/run_benchmark system_health.memory_mobile -v --upload-results --output-format=chartjson --browser=android-chromium --isolated-script-test-output=/b/swarming/w/iocV6kGy/output.json --isolated-script-test-chartjson-output=/b/swarming/w/iocV6kGy/chartjson-output.json
libdc1394 error: Failed to initialize libdc1394
(INFO) 2017-06-20 10:43:13,682 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb devices
(INFO) 2017-06-20 10:43:13,746 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb devices
(INFO) 2017-06-20 10:43:13,810 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb kill-server
(INFO) 2017-06-20 10:43:13,873 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb devices
(INFO) 2017-06-20 10:43:16,994 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb devices
(INFO) 2017-06-20 10:43:17,058 cmd_helper._ValidateAndLogCommand:158  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb kill-server
Cannot find browser of type android-chromium. To list out all available browsers, rerun your command with --browser=list
Traceback (most recent call last):
  File "../../testing/scripts/run_telemetry_benchmark_as_googletest.py", line 81, in main
    with open(chart_tempfile_name) as f:

The whole thing is failing in less around 7 seconds.

martiniss@, nednguyen@, any idea what might be happening?
 
At the bottom, there's this: 

DeviceUnreachableError: 0d88e86a43e4b0cc

Locals:
  args          : ['shell', '( dumpsys battery );echo %$?']
  check_error   : False
  cls           : <class 'devil.android.sdk.adb_wrapper.AdbWrapper'>
  cpu_affinity  : None
  device_serial : '0d88e86a43e4b0cc'
  m             : <_sre.SRE_Match object at 0x7f618425f0a8>
  output        : "error: device '0d88e86a43e4b0cc' not found\n"
  retries       : 2
  status        : 255
  timeout       : 30

I don't know why it's failing though. That's weird.
Status: WontFix (was: Untriaged)
Closing this as WontFix (obsolete)

Sign in to add a comment