1094988 - Check that LSan runs actually produce a report

Status: NEW

(Testing :: Mochitest, defect)

Description

[Andrew McCreight [:mccr8]]

Right now, if a process exits early, it just won't produce an LSan report.  Ideally, this would turn the tree orange, in much the same way as it will (hopefully) soon be for regular leak logs.  This will require adding additional parsing to figure out which processes produced a leak log, though I'm not sure this information is even there, then doing something similar to regular leak logs about checking which processes we created, and which were intentionally crashed. This may require a bit of work given that ASan runs are non-debug.

Comment 1

[Andrew McCreight [:mccr8]]

billm found that you can force it to do a leak check by calling __lsan_do_leak_check().  One approach would be to manually call that somewhere sufficiently late in the process, then print out a message afterwards.  That would at least ensure we got as far as the leak checking.  That does not really enforce that it actually did anything.