ToTAndroid x64 failing tests due to lack of swarming capacity |
|||||
Issue descriptionThis has been going on since a long time: https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid%20x64/?numbuilds=200 Example build: https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid%20x64/285 Tests fail like this: +------------------------------------------------------------------------+ | Shard 0 https://chromium-swarm.appspot.com/user/task/3b6555555ab97f10 | +------------------------------------------------------------------------+ +------------------------------------------------------------------------+ | End of shard 0 | | Pending: 3642.1s EXPIRED (lack of capacity) | +------------------------------------------------------------------------+ Do we not have any devices to run these tests on? If so we should probably disable testing on this bot and just make sure it keeps building. dpranke or maruel, do you know what's up with the swarming here or can you help point this in the right direction?
,
Feb 1 2018
Should we disable testing on this bot in the meantime, and just make sure it builds?
,
Feb 1 2018
Given that we haven't had working devices in well over a year, I think that'd be fair.
,
Feb 1 2018
Okay, I'll do that.
,
Feb 1 2018
There's literally 0 device_type:coho in the fleet, as seen on the task page "Fleet Capacity: 0 bots can run this task (0 dead, 0 quarantined)". There's plenty of arm64 devices in the fleet, just not this one.
,
Feb 1 2018
Note that this is about x64, not arm64 :-)
,
Feb 1 2018
Oh sorry. There's definitely something wrong with the fleet. https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&c=cpu&c=device_type&f=os%3AAndroid&f=cpu%3Ax86&l=300&q=devi&s=id%3Aasc
,
Feb 2 2018
Disabling the tests: https://chromium-review.googlesource.com/c/chromium/src/+/898983
,
Feb 2 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/96625b5017f2a61ea6a7633c85df39aba5b5f658 commit 96625b5017f2a61ea6a7633c85df39aba5b5f658 Author: Hans Wennborg <hans@chromium.org> Date: Fri Feb 02 13:25:03 2018 testing/buildbot: Disable tests on ToTAndroid x64 There are currently no devices available to run the tests, so the bot has been red for a long time. Disable the tests for now to make the bot green and ensure we don't regress being able to compile this config. Bug: 807966 Change-Id: I93442e6511a5c8c4e4a38346b1510b233743f593 Reviewed-on: https://chromium-review.googlesource.com/898983 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#534038} [modify] https://crrev.com/96625b5017f2a61ea6a7633c85df39aba5b5f658/testing/buildbot/chromium.clang.json [modify] https://crrev.com/96625b5017f2a61ea6a7633c85df39aba5b5f658/testing/buildbot/waterfalls.pyl
,
Feb 5 2018
The bot is green. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by thakis@chromium.org
, Feb 1 2018