New issue
Advanced search Search tips

Issue 669849 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Performance tests cannot be run on architectures which don't have android_tools binaries stored in cloud storage

Reported by djordje....@imgtec.com, Nov 30 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0

Steps to reproduce the problem:
1. build target android_tools (for MIPS architecture)
2. Connect MIPS android device
3. ./build/android/test_runner.py perf -vvv --release --single-step -- tools/perf/run_benchmark -vvvv --output-format=json kraken

What is the expected behavior?
Kraken performance test running on tablet

What went wrong?
Test failed with following message (more info in attached file):
NoPathFoundError: No file could be found locally, and no file to download from cloud storage for md5sum_device on platform android_mips

Did this work before? Yes https://chromium.googlesource.com/chromium/src/+/5db2dfe090fe92cd03e101d8592c360eceb3ebe2

Chrome version: refs/heads/master@{#432436}  Channel: dev
OS Version: 
Flash Version: Shockwave Flash 11.2 r202

MIPS android tools binaries are not stored in cloud storage, but can be built locally. These local binaries are properly detected for unit tests as a result of devil env initialization in build/android/devil_chromium.py, but they aren't detected here.

It seems that tools/perf is missing the part which initializes devil environment with local amends (something like tools/perf/chrome_telemetry_build/binary_dependencies.json)

First commit which introduced this issue:
https://chromium.googlesource.com/chromium/src/+/0c2a94ab87e6351b924a19932442e85a8f786fa0
 
/perf_test_fail.log
6.3 KB View Download

Comment 1 by ajha@chromium.org, Nov 30 2016

Labels: M-56
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.
Proposing catapult fix: https://codereview.chromium.org/2592803004/
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 13 2018

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