Device level targeting for triggered jobs in swarming |
||||||
Issue descriptionFor swarming the perf waterfall, we need to be able to consistently run a test on the same hardware for our results to be usable. For desktop, we target the id of the bot and consistently use that id every time the test is triggered. For android, we typically have 7 devices hooked up to one host, so need to be able to consistently run a test on the same device. One proposed solution is to implement a new dimension for device serial id but this rather brittle. Ideally we want to be able to implement this based on the device connection (1-7) and not the device that is connected. This is a bug to track the decision for this and the implementation as it is needed to swarm the chrome perf waterfall.
,
Nov 8 2016
,
Nov 15 2016
Can you elaborate on what you mean by 1:1 mapping for perf? Is that different from swarming adding a dimension for device serial id? We are blocked on this implementation now and I want to determine what the next steps are in implementation.
,
Nov 15 2016
No, it's reconstructing the fleet the same Skia did. I'll send internal links.
,
Nov 15 2016
We're not planning on reconstructing the fleet the way skia did; we want to get our existing hosts and devices on swarming, keeping the 7 devices per host. Does a dimension for device 1-7 seem like the right way to go?
,
Nov 15 2016
,
Jan 18 2017
Ping - please provide an update to your high priority bug. This bug is stale. Is it really P-1?
,
Feb 10 2017
,
Apr 10 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mar...@chromium.org
, Nov 3 2016