Jonathan Griffin (:jgriffin) Reporter
	Description • 10 years ago

Mochitest testruns get aborted if more than 4 tests time out.  We should consider something similar for Marionette.

Currently, in bug 971884, we're seeing a bunch of connection timeouts in gaiatest, which is causing the test run to go on for so long that buildbot kills it.  When this happens, we can't see gecko.log, and so have no idea what's really going on.

We should probably terminate a test run if we get 4 connection timeouts, or at least 4 connection timeouts in a row.  Possibly, we'd want to modify this behavior for long-running tests, so maybe something like a --max-timeouts argument would be appropriate.

	Malini Das [:mdas] - Away, not checking bugmail
	Comment 1 • 10 years ago

Bug 960436 will address the pipework required to let you have this behaviour. It will allow us to register handlers that will let you do some function X after Y failures of type Z has been seen. Once Bug 960436 is resolved, we can add specific handlers for gaiatest.

	David Burns :automatedtester
	Comment 2 • 7 years ago

[mass update] Setting Harness bugs to all P3

	Andreas Tolfsen ❲:ato❳
	Comment 3 • 6 years ago

We will probably never do this considering it is not a current problem.