зеркало из https://github.com/mozilla/gecko-dev.git
e0b02240a7
LeanSanitizer reports two kinds of leaks: direct and indirect. A leaked block that is pointed to by another leaked block is an "indirect leak", while one that isn't is a "direct leak". Often, indirect leaks are just things entrained by the "real" leak, but if two leaked blocks are in a cycle, then they both end up being indirect, so we need to report them, too. This patch makes it so that indirect LSan leaks are treated the same as direct leaks by Mochitests, which means they will turn the tree orange. There are a few existing indirect leaks of various severity, so I had add some suppressions. See those bugs for more details. --HG-- extra : rebase_source : 0269666f546b6e349bebf216771fc6dfa4d9487a |
||
|---|---|---|
| .. | ||
| config | ||
| crashtest | ||
| docker | ||
| gtest | ||
| instrumentation | ||
| luciddream | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| taskcluster | ||
| tools | ||
| tps | ||
| web-platform | ||
| xpcshell | ||
| README.txt | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| machine-configuration.json | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testsuite-targets.mk | ||
README.txt
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff