Joey Harrington

Reassigning subjobs or allocating new slaves would be an enhancement. Let's track the bug with stuck builds in #280.

That would be really cool. I was thinking about something similar but the one bump I never got past was how to ensure it runs on every slave. I guess...

Actually this may not be network flakiness since the output specifically says it "Could not fetch specified branch". Retries may still help since executing this fetch command manually a little...

Not that I know of. This falls under general network robustness improvements.

I think the reason this is happening is because `BuildRunner` calls `_cancel_build()` when it catches a `_BuildRunnerError`. And then we are also registering `_cancel_build()` as a teardown handler, and this...

@drobertduke @tjlee0909 Do you guys remember what the use case for this was?

> The build state will not be updated if the master thinks the slave disconnected before it is able to post back the status. This is probably the same issue...

Based on the conversation above, this issue could go one of two ways: - Any time the master receives a request from a slave that has been previously marked dead,...

I didn't mean that we should have the master deliberately ask the slave to shut down. I meant that whenever the master gets a state update call from a slave...

I'm not quite sure what you mean by "always raise a BadRequestError, even if the slave is alive" but I suspect we're on the same page. :dancing_men: