Bug 1519849 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #5)

> What did you mean by "special"?

Clearly this doesn't happen for all provisionerId/workerType/workerId combinations, otherwise we'd have a downtime. But since it happens consistently and reproducibly for the given provisionerId/workerType/workerId combination, that makes it special; it is behaving differently to the many production workers in running tasks happily at the moment without exhibiting this issue.
Revision 1 by
on 
(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #5)

> What did you mean by "special"?

Clearly this doesn't happen for all provisionerId/workerType/workerId combinations, otherwise we'd have a downtime. But since it happens consistently and reproducibly for the given provisionerId/workerType/workerId combination, that makes it special; it is behaving differently to the many workers that are happily running tasks at the moment in production without exhibiting this issue.

Back to Bug 1519849 Comment 8