New issue
Advanced search Search tips

Issue 738434 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Bisect jobs on monochrome-phone-perf-bisect are failing

Project Member Reported by alexilin@chromium.org, Jun 30 2017

Issue description

Bisect jobs that are using monochrome-phone-perf-bisect configuration constantly fail.

Probably, the reason is misconfiguration. All tests are run with option --browser=release that doesn't exist, apparently.

Log example:

/usr/bin/python /b/build/slave/monochrome-phone-perf-bisect/build/src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=5 --also-run-disabled-tests start_with_url.warm.startup_pages --device 0100542b27d7cc0c --output-dir=/b/build/slave/monochrome-phone-perf-bisect/build/bisect_results/febc18c9-a410-4775-a10c-438dc20e9720
...
Cannot find browser of type release. To list out all available browsers, rerun your command with --browser=list
 
Components: -Infra>Client>Android -Infra>Client>Perf Speed>Bisection
Cc: perezju@chromium.org
+perezju to see if he knows what browser that should be using
This is issue 724519 again. The answer: ... is complicated.
Mergedinto: 724519
Status: Duplicate (was: Untriaged)

Sign in to add a comment