Closed Bug 1296162 Opened 8 years ago Closed 8 years ago

330 seconds without output hangs in the reftest harness aren't highlighted

Categories

(Tree Management :: Treeherder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1261199

People

(Reporter: philor, Unassigned)

Details

I don't actually know whether Treeherder is supposed to be catching something in https://treeherder.mozilla.org/logviewer.html#?job_id=2125514&repo=autoland 01:57:56 INFO - REFTEST ERROR | file:///home/worker/workspace/build/tests/jsreftest/tests/jsreftest.html?test=ecma_3/Exceptions/binding-001.js | application timed out after 330 seconds with no output and isn't, or the reftest harness is supposed to be outputting something other than "REFTEST ERROR" or mozharness is supposed to be making that something other than an INFO line. Can't really say exactly when it started, but according to the summary of bug 1260338 it existed by the end of March, and in late January I filed a reftest 330 seconds bug, so around February or Marchish.
Sweet timing, finally filed it after knowing about it for five months, and the next day it's fixed. Separately. Without knowing that it was being fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.