mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-17 07:15:46 +00:00
03d4b0f51c
Currently the mochitest and reftest runners are forcing a timeout of 60s (or 900s for valgrind or debug builds) when calling `start_session` of Marionette. While this method still offers a timeout parameter, the timeout should be set via the `startup_timeout` argument for Marionette. Reason is that Marionette doesn't control the browser instance and is getting called right after the application gets launched. As such slow running builds can cause timeouts once it takes longer than 60s for the Marionette server to get started. By using `startup_timeout` the timeout will even be configurable via the command line and mozharness config files. MozReview-Commit-ID: EV7GklBcJjU --HG-- extra : rebase_source : 9d3c623c49deb92d68c40ba4410c812c864e06bd |
||
|---|---|---|
| .. | ||
| awsy | ||
| config | ||
| crashtest | ||
| firefox-ui | ||
| geckodriver | ||
| gtest | ||
| instrumentation | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webdriver | ||
| xpcshell | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| README.txt | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testsuite-targets.mk | ||
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