Meant to say, the issue per the log here seems to be "Got timeout in harness", which it notes "may indicate a hang" but in this case it doesn't seem to indicate a hang; we're still running tests up tot he last second, and it's not like we got stuck in a test for an inordinate amount of time. It seems the time-needed-for-code-coverage-and-these-tests is substantially longer than the 9 minutes (really, 5 minutes after 4 minutes of spin-up time) that we're apparently allotting for this task.
Bug 1835219 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Meant to say, the issue per the log here seems to be "Got timeout in harness", which it notes "may indicate a hang" but in this case it doesn't seem to indicate a hang; we're still running tests up to the last second, and it's not like we got stuck in a test for an inordinate amount of time. It seems the time-needed-for-code-coverage-and-these-tests is substantially longer than the 9 minutes (really, 5 minutes after 4 minutes of spin-up time) that we're apparently allotting for this task.