win-high-dpi bisects not being routed correctly to win-high-dpi bisectors |
||||||
Issue descriptionLink to buildbot status page: https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect The bisect that I launched (for https://bugs.chromium.org/p/chromium/issues/detail?id=644258) returned with a failure due to no power data. Infra-labs, could you please make sure that the BattOr is attached, blinking, and showing up as "USB Serial Device (COM#)" in the device manager? If it's connected and blinking, it may need device drivers installed as per the instructions here (https://docs.google.com/document/d/1_IdRUB8GKux40GsF9herpBAkktO4UjPYDzXkm5T-PI8/edit#heading=h.2p92qzv7j896). If you could also check this for the other win-power-high-dpi bisectors and win-power-high-dpi trybots, I'd very much appreciate it! That way, we can make sure we don't have to look at this again in the future.
,
Sep 6 2016
+sullivan, dtu I don't believe we have deployed any BattORs in golo for m4 bots. Only BattORs we've deployed are all in MTV.
,
Sep 6 2016
,
Sep 6 2016
My guess would be that we do not have the drivers updated on this, like charlie said above. We had a similar problem on the main waterfall win-power-high-dpi battor machines.
,
Sep 6 2016
As Vince mentioned in #2, no -m4 bots have battOrs, so it's WAI.
,
Sep 6 2016
I'm confused: I thought that we had BattOrs attached to the full deployment of win-power-high-dpi bots, which included the 5 perf bots, the 3 bisectors, and 2 try bots?
,
Sep 6 2016
build242-m4 is a rack mounted Dell r220 server. It does not have a battery as a power source.
,
Sep 7 2016
win-power-high-dpi bisector should be run on https://uberchromegw.corp.google.com/i/tryserver.chromium.perf/builders/winx64_high_dpi_perf_bisect ?
,
Sep 14 2016
Changing the scope of this bug: it now appears that it has to do with win-high-dpi bisects not being correctly routed to the win-high-dpi bisectors
,
Sep 14 2016
Prasad, I don't see winx64_high_dpi_perf_bisect in the list when I try to bisect here: https://chromeperf.appspot.com/report?sid=d31dfed134e2f31cdc9d30994559076fab1e0c1788ced569b9dd8abf12097d51&start_rev=414994&end_rev=416614 It should show up as default. Would you mind taking a look? Also is there a doc on all the places that need to be updated when we add a new bisector?
,
Sep 14 2016
I modified bisect_bot_map edit_config in Perf dashboard, now the win-high-dpi bisects being routed correctly to win-high-dpi winx64_high_dpi_perf_bisect https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_high_dpi_perf_bisect/builds/22 I'll work on the short doc about things to take care when we add a new bot on tryserver.chromium.perf.
,
Sep 15 2016
Great - thank you so much Prasad!
,
Sep 15 2016
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by charliea@chromium.org
, Sep 6 2016