зеркало из https://github.com/mozilla/gecko-dev.git
b0a07b2297
When using unittest rather than mozunit, something seems to be holding onto the XPCShellTests, which keeps the subprocess objects around even after we shut them down, and in turn, that keeps the pipe file descriptors associated with the subprocesses around, effectively leaking them for the duration of the entire selftest, which in some cases could exhaust the system resources allocated to the selftest process. Differential Revision: https://phabricator.services.mozilla.com/D84471 |
||
|---|---|---|
| .. | ||
| dns-packet | ||
| example | ||
| moz-http2 | ||
| node-http2 | ||
| node-ip | ||
| README | ||
| dbg-actors.js | ||
| head.js | ||
| mach_commands.py | ||
| mach_test_package_commands.py | ||
| moz.build | ||
| python.ini | ||
| remotexpcshelltests.py | ||
| runxpcshelltests.py | ||
| selftest.py | ||
| xpcshellcommandline.py | ||
README
Simple xpcshell-based test harness converted from netwerk/test/unit Some documentation at http://developer.mozilla.org/en/docs/Writing_xpcshell-based_unit_tests See also http://wiki.mozilla.org/SoftwareTesting:Tools:Simple_xpcshell_test_harness