Open Bug 1848850 Opened 1 year ago Updated 4 months ago

[meta] [wdspec] Improve crash detection

Categories

(Remote Protocol :: Marionette, task)

task

Tracking

(Not tracked)

People

(Reporter: whimboo, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

With bug 1848799 we will report a failing test due to a crashed Firefox as CRASH. But the currently detection by the wptrunner harness and geckodriver isn't that great especially for slow running builds. We should improve the detection rate:

  1. geckodriver should not fail with a message like: Failed to decode response from marionette when the browser process does no longer exist.
  2. For slow builds the shutdown after the crash might take longer. Take this into account when looking for crashes.
  3. On Android the state is unknown and it needs to be investigated what's necessary to do here.

If geckodriver would know about a crash it could raise a different kind of error (as the one mentioned under 1.), so that the pytestrunner and wptrunner can handle it appropriately. There is already bug 1433495 to get minidump files saved to a specific folder and to let them survive from the temporary profile.

Depends on: 1433495
Summary: [wdspec] Improve crash detection → [meta] [wdspec] Improve crash detection
Blocks: 1900066
No longer blocks: 1851160
You need to log in before you can comment on or make changes to this bug.