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

Issue 687995 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

WebRTC Android Perf bots failing on "pm dump" not being a valid command

Project Member Reported by ehmaldonado@chromium.org, Feb 2 2017

Issue description

WebRTC Android Perf bots have been failing for a while now with:

AdbShellCommandFailedError: (device: 0274379bdbcb06ae) shell command run via adb failed on the device:
  command: pm dump org.chromium.native_test | grep dataDir=; echo "PIPESTATUS: ${PIPESTATUS[@]}"
  exit status: [0, 1]
  output:
  - Error: unknown command 'dump'

Full logs at https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28J%20Nexus4%29/builds/489/steps/webrtc_perf_tests/logs/stdio

 
Components: Infra
It seems to have started with https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28J%20Nexus4%29/builds/387 and it onlyl affects our Nexus 4 perf bot, no other.
I can't say for sure that's the first place it happened (these bots don't seem to archive logs at logdog for some reason) but it's been red ever since.
Components: Infra>Labs
Summary: WebRTC Android Perf bots failing on "pm dump" not being a valid command (was: WebRTC Android Perf bots are failing.)
Maybe the labs folks have seen this before?
Looks like pm dump is not supported on jb?
Let me know if you want the N4's updated to L?
Hmm, part of the idea with these bots were to have coverage on JB, but it's fine to upgrade them if that solves this problem.
Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Since the N4's have been upgrade to L things are green.   Wanna rename the builder?
Cc: pschmidt@chromium.org
Owner: kjellander@chromium.org
Yes, I'll take of it. Thanks for doing the upgrade!
Project Member

Comment 10 by bugdroid1@chromium.org, Feb 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/819689e7a5e5396e1236f6804539b3a282ceee28

commit 819689e7a5e5396e1236f6804539b3a282ceee28
Author: Henrik Kjellander <kjellander@chromium.org>
Date: Mon Feb 06 06:41:21 2017

WebRTC: Rename bots after upgrading Nexus4 devices.

The Nexus 4 devices were upgraded from JB->L due to
errors caused by other infrastructure changes.
Rename the builder and update the perf ID.

BUG= 687995 
TBR=ehmaldonado@chromium.org

Change-Id: I10e4dd8592a15f44527d02b57929d8b43ec21ba2
Reviewed-on: https://chromium-review.googlesource.com/438304
Reviewed-by: Henrik Kjellander <kjellander@chromium.org>
Commit-Queue: Henrik Kjellander <kjellander@chromium.org>

[modify] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/masters/master.client.webrtc.perf/master.cfg
[modify] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/scripts/slave/recipes/webrtc/standalone.expected/client_webrtc_perf_android32_builder_forced.json
[rename] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/scripts/slave/recipes/webrtc/standalone.expected/client_webrtc_perf_android32_tests__l_nexus4_.json
[modify] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/scripts/slave/recipe_modules/webrtc/builders.py
[modify] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/scripts/slave/recipes/webrtc/standalone.expected/client_webrtc_perf_android32_builder.json
[modify] https://crrev.com/819689e7a5e5396e1236f6804539b3a282ceee28/masters/master.client.webrtc.perf/slaves.cfg

Status: Fixed (was: Assigned)

Sign in to add a comment