Open simonhatch opened 6 years ago
Simon explains on the bug:
"Request was aborted after waiting too long to attempt to service your request."
AFAIK this can happen when a new instance is spun up but isn't ready before the 10s limit, leaving the job in limbo.
crbug.com/830827
What I think happened is the request was aborted after 10s, and since there's no retry set on job tasks this went into limbo.
@dave-2