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

Issue 594545 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
qyears...@chromium.org
█ nednguyen@chromium.org
jbudorick@chromium.org
█ aiolos@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

android_one_perf_bisect does not have android-chromium browser

Project Member Reported by perezju@chromium.org, Mar 14 2016 
Trying to run a bisect for issue 594083, bot fails with:

BrowserFinderException: No browser found.

Available browsers:
android-jb-system-chrome
reference
https://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1207/steps/Gathering%20Reference%20Values/logs/stdio

Command was: tools/perf/run_benchmark -v --browser=android-chromium --output-format=buildbot --also-run-disabled-tests memory.memory_health_plan --pageset-repeat 5

Any idea why this would fail?

Comment 1 by qyears...@chromium.org, Mar 17 2016

Cc: jbudorick@chromium.org nednguyen@chromium.org
Components: Tests>AutoBisect Tests>Telemetry
Hmm, I'm not sure -- normally we'd definitely expect android-chromium to be in the list of available browsers, I believe.

I'm not sure how that browser gets installed onto the device, but maybe there was an error while installing the browser onto the device?

CC Ned, John in case you have more hints about why this might have happened.

If we don't see this again, maybe it could be a rare flaky failure?

Comment 2 by nedngu...@google.com, Mar 17 2016

Cc: aiolos@chromium.org
+Kari: can you investigate what's happening here?

Comment 3 by pras...@chromium.org, Mar 17 2016

Labels: triaged
Status: Available (was: Untriaged)

Comment 4 by perezju@chromium.org, Mar 18 2016

Blocking: -594083

Comment 5 by perezju@chromium.org, Mar 29 2016

Status: WontFix (was: Available)
I see some recent runs on https://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/ that seem to have worked and also used --browser=android-chromium. So, somehow things just started working again?

Comment 6 by benhenry@chromium.org, Feb 3 2017

Components: Speed>Bisection

Comment 7 by benhenry@chromium.org, Mar 10 2017

Components: Speed>Benchmarks>Waterfall
Labels: -Performance-Waterfall
►

Sign in to add a comment