Open Bug 1062918 Opened 6 years ago Updated 5 years ago
.js logs a timeout that doesn't contribute to job status
I looked at this a bit last night. At some point TestRunner.js forcefully ends a test an over time test in progress in testharness.js in a way that doesn't result in TestRunner.js updating its UI (and therefore the summary counts), but in a way that I couldn't replicate locally. Setting the job status from parsing out summary counts from the UI seems inherently fragile. Missing these kinds of failures will not be possible once we're consuming raw logs directly in mozharness.
You need to log in before you can comment on or make changes to this bug.