Open Bug 1259330 Opened 8 years ago Updated 2 years ago

Intermittent e10s browser_devices_get_user_media.js | Test timed out

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

defect

Tracking

()

Tracking Status
e10s + ---

People

(Reporter: philor, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Summary: Intermittent browser_devices_get_user_media.js | Test timed out → Intermittent e10s browser_devices_get_user_media.js | Test timed out
Blocks: e10s-tests
tracking-e10s: --- → +
The log says:
JavaScript Error: "remote browser crashed while on https://example.com/browser/browser/base/content/test/general/get_user_media.html"
at https://treeherder.mozilla.org/logviewer.html#?job_id=24506616&repo=mozilla-inbound#L10655
so I don't think this is a Device Permissions issue. Unfortunately I don't see a stack in the log.
Component: Device Permissions → WebRTC: Audio/Video
Product: Firefox → Core
Looking like it might be fixed...
Rank: 25
Priority: -- → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3

:jib - this test is one of the blockers for the migration from macosx1010 to macosx1014 for mochitest-browser-chrome. It may have to be disabled for macosx1014 due to the persistent failure there. Could you pass the ni to someone who may be able to comment on the failure for macosx1014, thanks!

Flags: needinfo?(jib)

These seem quite rare. Comment 21 was 17 days ago, and no longer have logs available. Do you have a more recent log?

Flags: needinfo?(jib)

:jib - certainly. This push contains mochitest-browser-chrome run on macosx1014: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&searchStr=browser-chrome%2Cmacosx1014&revision=9fbed80016abf084ade73673fc8c2ddcf59b0955

Failure log: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&searchStr=browser-chrome%2Cmacosx1014&revision=9fbed80016abf084ade73673fc8c2ddcf59b0955

As of this try run, this failure appears to be a permafail on macosx1014 shippable and debug platforms. I suspect it is rare because it is only reproducible (again) on macosx1014.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.