зеркало из https://github.com/mozilla/gecko-dev.git
ffde3c272c
We're seeing a lot of cases where our "check for zombie child processes" check is finding live processes, but the minidumps that we get from such processes are nonsense, and don't even feature Firefox symbols. The working theory at this point, courtesy of bobowen, is that child processes that we launch are getting closed during the test runs, completely normally, and then we are finding other (non-Firefox) live processes with the PIDs that were used for Firefox child processes at the end of the test run. This scenario is plausible due to Windows's aggressive reuse of PIDs. We don't see the same behavior on our Unix test machines because Linux (and OS X, apparently) are not nearly as aggressive in reusing PIDs. Since we should be ensuring that any live processes are actually Firefox processes anyway, let's add the appropriate check. If the check works to reduce the incidence of zombiecheck failures, that's great! If not, we've at least made our test runner more robust and can investigate other possibilities for these intermittent failures. |
||
---|---|---|
.. | ||
BrowserTestUtils | ||
MochiKit | ||
baselinecoverage | ||
chrome | ||
dynamic | ||
embed | ||
manifests | ||
pywebsocket | ||
ssltunnel | ||
static | ||
tests | ||
README.txt | ||
ShutdownLeaksCollector.jsm | ||
__init__.py | ||
api.js | ||
bisection.py | ||
browser-harness.xul | ||
browser-test.js | ||
chrome-harness.js | ||
chunkifyTests.js | ||
favicon.ico | ||
gen_template.pl | ||
harness.xul | ||
install.rdf | ||
leaks.py | ||
mach_commands.py | ||
mach_test_package_commands.py | ||
manifest.json | ||
manifest.webapp | ||
manifestLibrary.js | ||
mochitest-e10s-utils.js | ||
mochitest_options.py | ||
moz.build | ||
nested_setup.js | ||
pywebsocket_wrapper.py | ||
redirect.html | ||
runjunit.py | ||
runrobocop.py | ||
runtests.py | ||
runtestsremote.py | ||
schema.json | ||
server.js | ||
shutdown-leaks-collector.js | ||
start_desktop.js |
README.txt
See https://developer.mozilla.org/en/docs/Mochitest for detailed information on running and writing mochitests.