Get bisect working for webrtc_perf_tests on master.client.webrtc.perf (WebRTCPerf) |
||||
Issue descriptionWe would like to be able to auto bisect into: https://chromeperf.appspot.com/report?sid=6ff9918bf09a3859eefd6a4f4e91c40cc29927f45973e4ed8f2b75d6ba125262&rev=21983 What would it take to get that working?
,
Feb 23 2018
+dtu for more details We're working on supporting other waterfalls at the moment, will hopefully be done by end of Q1. Up front Pinpoint requires a few things: * A builder setup to receive buildbucket requests. * Devices available via a swarming pool. But if this is pretty much using the same setup as the perf waterfall, ie. we can just map your bots to something from chromium.perf, and you're fine using the builds generated by chromium.perf this might be as simple as whitelisting and mapping the names. In theory we should be able to start bisects in another depot, the support was built-in to Pinpoint, although we haven't tried yet.
,
Feb 23 2018
Looks like the tests are run through Buildbot, and are not Swarmed, so that might be the first step.
,
Feb 26 2018
Right, they're not swarmed for Android (at least yet), but they are for the desktop platforms: https://uberchromegw.corp.google.com/i/client.webrtc.perf/builders/Linux%20Trusty Can we configure bisect for the desktop platforms first, or is it a requirement to move to swarming for Android first?
,
Mar 9 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by phoglund@chromium.org
, Feb 23 2018