Closed Bug 1351931 Opened 8 years ago Closed 7 years ago

Intermittent test_crash.py TestCrashInSetUp.test_crash_in_setup | AssertionError: "Process crashed" does not match "Process killed because the connection to Marionette server is lost. Check gecko.log for errors (Reason: Connection timed out after 10s)"

Categories

(Testing :: Marionette Client and Harness, defect)

Version 3
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1377030

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

We should crash immediately for those unit tests but somehow it has been taken more than a minute: > 09:40:13 INFO - TEST-START | test_crash.py TestCrashInSetUp.test_crash_in_setup > 09:41:29 ERROR - TEST-UNEXPECTED-ERROR | test_crash.py TestCrashInSetUp.test_crash_in_setup | AssertionError: "Process crashed" does not match "Process killed because the connection to Marionette server is lost. Check gecko.log for errors (Reason: Connection timed out after 10s)" Maybe something wrong with the machine the test was running on? I would need more data for that.
:whimboo this test has failed consistently for a few months, it seems to have picked up slightly in frequency in the last few weeks for osx, is there someone who could take a brief look at this?
Flags: needinfo?(hskupin)
With bug 1223277 I kinda change the implementation of the unit crash tests for Marionette. Lets wait until this got landed.
Depends on: 1223277
Flags: needinfo?(hskupin)
This should be blocked on bug 1376795.
Depends on: 1376795
Bug 1377030 is more active these days.
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: leave-open
Resolution: --- → DUPLICATE
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
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.