Swarming bots which fail to reboot should be quarantined |
|||||
Issue descriptionSwarming bots which fail to reboot should be quarantined I set up this bot incorrectly (typo in visudo), and it was unable to reboot itself: https://chromium-swarm.appspot.com/restricted/bot/skiabot-macmini-10_8-002 The bot would attempt to reboot itself every 15 minutes and did not attempt to pick up any tasks. It was not marked as quarantined or dead. In my opinion, if the failure to reboot is going to cause the bot not to pick up any tasks, the bot should be quarantined.
,
May 12 2016
Sure, could you point me to where I'd make the change?
,
May 12 2016
These two need to somehow communicate: https://github.com/luci/luci-py/blob/master/appengine/swarming/swarming_bot/api/bot.py#L112 https://github.com/luci/luci-py/blob/master/appengine/swarming/swarming_bot/bot_code/bot_main.py#L106 In general the call site is https://github.com/luci/luci-py/blob/master/appengine/swarming/swarming_bot/bot_code/bot_main.py#L457
,
Jun 2 2016
,
Jun 21 2016
There's an owner on this bug but the status != Assigned. Fixing. If you feel you don't own this bug, please remove yourself as the owner and mark it as "Available" or "Untriaged".
,
Jan 18 2017
Pri-3 that hasn't been updated in 180+ days with status=assigned or started? Get real. I've unassigned you and marked this available. If you're truly working on this, update the priority and reassign yourself or someone who is working on this.
,
Jan 18 2017
Reassigning to Eric. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mar...@chromium.org
, May 12 2016