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

Issue 595740 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 27 days ago
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Dashboard not properly selecting Nexus 5X for bisect

Project Member Reported by sullivan@chromium.org, Mar 17 2016

Issue description

See context in bug 595703 -- looks like the dashboard defaults to N5 and not N5X. Prasad, can you take a look?
 
Blocking: 595703
Cc: petrcermak@chromium.org
Status: Started (was: Unconfirmed)
Nexus5X was missing int storage map association between bot names and bisect bot names. I added it to the config and it is now displayed in the dropdown.

Please note: Although Nexus5x bisect bot is displayed in the dropdownlist, this is not selected as default when we want to run bisect on nexus5x perf regression.  I'll discuss with qyearsley, about the possible to fix for this.

Meanwhile please select Nexus5x manually from the dashboard.

Blocking: -595703
Blocking: -595703
We found what appears to be the cause for this; fix in https://codereview.chromium.org/1806333007
Status: Fixed (was: Started)
I'm pretty sure we verified this as fixed now.
Components: Speed>Bisection

Sign in to add a comment