791590 - Add stackwalk dumps when unexpected crashes found in JS test harnesses

Status: RESOLVED WONTFIX

(Testing :: General, defect)

Description

[Josh Matthews [:jdm]]

Currently, there are some cases wherein we see backtraces from crashes that occur in certain test harnesses. I'm not sure precisely when these cases are, but the code to launch the stackwalker lives in automationutils.py: http://mxr.mozilla.org/mozilla-central/source/build/automationutils.py#168

We also have code in TestRunner that notes unexpected minidump files and cleans them up: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/tests/SimpleTest/TestRunner.js#420 This doesn't show us any details about the crash that actually occurred.

At minimum, I feel like we should be able to duplicate the python code in JS (since we do have the ability to launch processes and collect their output) and improve the experience immeasurably.

Comment 1

[(not currently active) Ted Mielczarek]

I'm not really wild about duplicating this logic. The only case where this should occur is if we have a child process that crashes.

Comment 2

[Josh Matthews [:jdm]]

Ah, yes, that is what people on the graphics team were having happen when they were playing with out-of-process compositing patches and IPC tests were hanging.

Comment 3

[Geoff Brown [:gbrown]]

Mass closing bugs with no activity in 2+ years. If this bug is important to you, please re-open.