Closed Bug 513010 Opened 17 years ago Closed 16 years ago

output stack backtraces when killing tests that time out

Categories

(Testing :: Mochitest, defect)

Product:
Testing
Component:
Mochitest
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 501034

People

(Reporter: karlt, Unassigned)

Details

Now that we get crash stacks on test machines, it should be possible to get a backtrace when the process is killed due to an apparent hang. (In the future a profile sample may provide more information but a single stack may be easy to produce and would be helpful.) This might be implemented simply by first trying to kill the process with a signal that will cause a stack dump. SIGTERM or SIGQUIT sound like sensible signals but I don't know which signals currently produce stacks. Maybe SIGABRT would produce a stack more easily.
This is important. Unidentified hangs cause random orange all the time, and getting stack traces or samples would help a lot.
The test harnesses are probably the right place to do this in.
Component: Release Engineering → Mochitest
Product: mozilla.org → Testing
QA Contact: release → mochitest
Version: other → Trunk
Oh hey, I fixed this already.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
V.Duplicate
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.