Revision df7e6cdf297c06a05b5a116f51fb203cda295809 authored by James Graham on 19 July 2018, 18:11:53 UTC, committed by jgraham on 23 July 2018, 13:35:19 UTC
LSAN data differs from existing expectation data because the data is only generated when the browser exits, so the problems reported can happen at any point in the current session. We use the `scope` property in the log message to determine the path to a __dir__.ini file that covers all the tests run in the session, and add the LSAN exclusion rules to there. The rules themselves are generated by taking the topmost frame of any stack that's reported as unexpectedly leaking, and adding that to the list of permitted frames in the lsan-allowed property. We never remove entries from this list since intermittents may be present which won't appear on a specific run. Instead we rely on humans fixing the issues to also clean up the expectation files. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232 gecko-commit: 9e8a66385f66f89f8cf2c9a18edf008496fa89fa gecko-integration-branch: mozilla-inbound gecko-reviewers: maja_zf
1 parent 91803e3
wpt
#!/usr/bin/env python
if __name__ == "__main__":
from tools.wpt import wpt
wpt.main()
Computing file changes ...
