Dashboard not properly selecting Nexus 5X for bisect |
|||||||
Issue descriptionSee context in bug 595703 -- looks like the dashboard defaults to N5 and not N5X. Prasad, can you take a look?
,
Mar 17 2016
,
Mar 17 2016
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.
,
Mar 17 2016
Here is the Job I kicked out via dashboard https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/12
,
Mar 17 2016
,
Mar 17 2016
,
Mar 18 2016
We found what appears to be the cause for this; fix in https://codereview.chromium.org/1806333007
,
Mar 31 2016
I'm pretty sure we verified this as fixed now.
,
Feb 3 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sullivan@chromium.org
, Mar 17 2016