mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
18a2cf7cb0
I noticed in automation logs that we always wait about 1s for httpd.js to be ready -- this is the minimum we could wait if we wait at all, because we poll every second. Bringing the polling interval down to 100ms locally shows we succeed after waiting just once. This is a perceptible speedup, and will have an effect for every dir now that we run-by-dir. |
||
|---|---|---|
| .. | ||
| BrowserTestUtils | ||
| chrome | ||
| dynamic | ||
| manifests | ||
| MochiKit | ||
| pywebsocket | ||
| ssltunnel | ||
| static | ||
| tests | ||
| b2g_start_script.js | ||
| bisection.py | ||
| browser-harness.xul | ||
| browser-test-overlay.xul | ||
| browser-test.js | ||
| cc-analyzer.js | ||
| chrome-harness.js | ||
| chunkifyTests.js | ||
| gen_template.pl | ||
| harness.xul | ||
| install.rdf | ||
| jar.mn | ||
| jetpack-addon-harness.js | ||
| jetpack-addon-overlay.xul | ||
| jetpack-package-harness.js | ||
| jetpack-package-overlay.xul | ||
| leaks.py | ||
| mach_commands.py | ||
| mach_test_package_commands.py | ||
| Makefile.in | ||
| manifest.webapp | ||
| manifestLibrary.js | ||
| mochitest_options.py | ||
| mochitest-e10s-utils.js | ||
| moz.build | ||
| nested_setup.js | ||
| pywebsocket_wrapper.py | ||
| README.txt | ||
| redirect.html | ||
| runrobocop.py | ||
| runtests.py | ||
| runtestsb2g.py | ||
| runtestsremote.py | ||
| server.js | ||
| shutdown-leaks-collector.js | ||
| ShutdownLeaksCollector.jsm | ||
See https://developer.mozilla.org/en/docs/Mochitest for detailed information on running and writing mochitests.