LSAN and ASAN failures now show up as something better than just a crash, but there's still room for improvement. See bug 981023 comment 11 and 12 for some ideas. The SUMMARY line is output by LSAN itself, so I assume this would require modifying the test harness layer to parse that and output something else.

The LSan output is pretty good now. I think the thing to do here is to generalize the LSan report parser so it can be used for ASan reports, then back out the changes in bug 981023. One tricky aspect is the intentional crashes that happen (in the js-ctypes tests, if not other places) shouldn't display an error.