зеркало из https://github.com/mozilla/gecko-dev.git
8583436ea5
We are seeing failures starting websocketProcessBridge due to the port being in use. It is most likely a previously started websocketProcessBridge process that is using the port. On Windows, mozprocess.kill() calls TerminateJobObject/TerminateProcess and GetExitCodeProcess, but these are asynchronous and don't wait for the process to actually exit. Adding a wait call should guarantee the process has exited before continuing which will hopefully ensure the port is free by the time we start an additional websocketProcessBridge. MozReview-Commit-ID: HGyjEsy1Ons --HG-- extra : rebase_source : f56034e1fc0febae07d9b2728eded0a48975baca |
||
|---|---|---|
| .. | ||
| BrowserTestUtils | ||
| MochiKit | ||
| chrome | ||
| dynamic | ||
| embed | ||
| manifests | ||
| pywebsocket | ||
| ssltunnel | ||
| static | ||
| tests | ||
| Makefile.in | ||
| README.txt | ||
| ShutdownLeaksCollector.jsm | ||
| __init__.py | ||
| bisection.py | ||
| bootstrap.js | ||
| browser-harness.xul | ||
| browser-test-overlay.xul | ||
| browser-test.js | ||
| chrome-harness.js | ||
| chunkifyTests.js | ||
| gen_template.pl | ||
| harness.xul | ||
| install.rdf | ||
| jar.mn | ||
| leaks.py | ||
| mach_commands.py | ||
| mach_test_package_commands.py | ||
| manifest.webapp | ||
| manifestLibrary.js | ||
| mochitest-e10s-utils.js | ||
| mochitest_options.py | ||
| moz.build | ||
| nested_setup.js | ||
| pywebsocket_wrapper.py | ||
| redirect.html | ||
| rungeckoview.py | ||
| runrobocop.py | ||
| runtests.py | ||
| runtestsremote.py | ||
| 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.