Open Bug 1464989 Opened 6 years ago Updated 2 years ago

Marionette has to report startup crashes instead of failing with "Failure during harness execution"


(Testing :: Marionette Client and Harness, enhancement, P3)



(Not tracked)


(Reporter: whimboo, Unassigned)


(Depends on 1 open bug)


Yesterday we had a busted commit for Windows builds:

Mochitests reported the following for the first start of Firefox where Marionette is active:

> PROCESS-CRASH | | application crashed [@ PLDHashTable::Search(void const *)]

Instead Marionette and FxUI tests reported:

> Failure during harness execution

This is suboptimal because it doesn't let us directly see the underlying problem, and as such failures are getting wrongly starred for bug 1407390.
`raise_for_port` actually checks the process status but due to bug 1433905 it's not correct and as such the loop doesn't exit early but with a socket timeout error:

Once bug 1433905 is fixed we would have to check again if we actually make use of mozcrash under such a condition. The following debug builds would help which seem to crash a lot during startup:

Depends on: 1433905
Before we can continue here we have to make sure to be able to track and follow detached processes. So bug 1434878 needs to be finished off first.
Depends on: 1434878
Severity: normal → S3
Product: Testing → Remote Protocol
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.