mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-19 16:25:38 +00:00
f53f58d169
Currently mochitest looks for a test_start log action and stores the name of the test in an instance variable. In the event of a timeout/hang, this string is used in the log to help people try and narrow down where it happened. However, there are a couple cases it can be misleading: 1) If the hang happens during shutdown, it looks like it was the last test's fault (it probably isn't) 2) If the hang happens in-between tests, it looks like the test timed out We should make the string more descriptive. I propose that when we get a test_end action, we change it to <test> (finished). And when we get the test end action of the last test, we change it to "Last test finished". This way it narrows down where the hang happened even further. MozReview-Commit-ID: B6g8JrIJuJw Differential Revision: https://phabricator.services.mozilla.com/D1885 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
baselinecoverage | ||
BrowserTestUtils | ||
chrome | ||
dynamic | ||
embed | ||
manifests | ||
MochiKit | ||
pywebsocket | ||
ssltunnel | ||
static | ||
tests | ||
__init__.py | ||
bisection.py | ||
bootstrap.js | ||
browser-harness.xul | ||
browser-test.js | ||
chrome-harness.js | ||
chunkifyTests.js | ||
favicon.ico | ||
gen_template.pl | ||
harness.xul | ||
install.rdf | ||
jar.mn | ||
leaks.py | ||
mach_commands.py | ||
mach_test_package_commands.py | ||
manifest.webapp | ||
manifestLibrary.js | ||
mochitest_options.py | ||
mochitest-e10s-utils.js | ||
moz.build | ||
nested_setup.js | ||
pywebsocket_wrapper.py | ||
README.txt | ||
redirect.html | ||
rungeckoview.py | ||
runjunit.py | ||
runrobocop.py | ||
runtests.py | ||
runtestsremote.py | ||
server.js | ||
shutdown-leaks-collector.js | ||
ShutdownLeaksCollector.jsm | ||
start_desktop.js |
See https://developer.mozilla.org/en/docs/Mochitest for detailed information on running and writing mochitests.