Implement DUT_FAILURE logic for Android in V8 test launchers (run_perf.py, run_test.py) |
|||||
Issue descriptionE.g.: https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Android%20Arm64%20-%20N5X/1771 https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Android%20Arm64%20-%20N5X/1763 One shard has no device and the test runner chokes on it: https://chromium-swarm.appspot.com/task?id=41258b5917d62010&refresh=10&show_raw=1 Is it possible to return in a way so that swarming retries this task on another host?
,
Nov 15
AFAIK swarming should quarantine bots that have not bot device connected. So perhaps it's a bug in swarming, not in V8?
,
Nov 15
,
Nov 15
,
Nov 15
Many bot_config do that, but not all.
,
Nov 16
,
Nov 20
> Many bot_config do that, but not all. Do you mean that there is some hook that we can implement for this in V8 swarming bot_config script? How do other bot_configs do that?
,
Nov 20
This bot (build335-m1--device2) is already in pool:Chrome on Android, so it already has the logic. Still, the device can still go MIA occasionally. Issue 902807 is really the long term fix.
,
Nov 21
Ah, sorry, just read the blockedon file. Makes sense, then this bug is about implementing DUT_FAILURE logic in our test launcher.
,
Dec 17
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mar...@chromium.org
, Nov 13