Closed Bug 1227386 Opened 9 years ago Closed 2 years ago

Intermittent test_peerConnection_asymmetricIsolation.html | Test timed out

Categories

(Core :: WebRTC, defect, P4)

Product:
Core
Component:
WebRTC
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: philor, Unassigned)

References

(Depends on 1 open bug, Regression)

Details

(Keywords: intermittent-failure, regression)

backlog: --- → webrtc/webaudio+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
gUM seems to be timing out here.
See Also: → 1226343
Depends on: gUM_timeout

The patch for Bug 1652463, turned this into a perma-fail.
That patch only adds a rule which allows the socket process to open the server side of our IPC pipes.
My understanding (from the bug) was that it wouldn't do anything unless network.http.network_access_on_socket_process.enabled is true.

bwc - any ideas why that might cause an issue with this test? ... my only guess is some sort of timing issue

Flags: needinfo?(docfaraday)

So this is the first test that tries to use the socket process in any significant way. We use the socket process iff both the "network.process.enabled" and "media.peerconnection.mtransport_process" are true. Maybe there is a failure or delay starting the socket process sometimes...

Flags: needinfo?(docfaraday)

(In reply to Byron Campen [:bwc] from comment #47)

So this is the first test that tries to use the socket process in any significant way. We use the socket process iff both the "network.process.enabled" and "media.peerconnection.mtransport_process" are true. Maybe there is a failure or delay starting the socket process sometimes...

Thanks bwc - I'll get kershaw to take a look at this then.

kershaw - this became a perma-fail, when we tried to allow the thing you required in bug 1652463, so it's blocking that bug.
Can you take a look please.

Flags: needinfo?(kershaw)

(In reply to Bob Owen (:bobowen) from comment #50)

kershaw - this became a perma-fail, when we tried to allow the thing you required in bug 1652463, so it's blocking that bug.
Can you take a look please.

Sorry for the delay.
I've tried to add MOZ_LOG=socketprocess:5 to this try run, but I can't see any logs. I'll manually add some logs and try again.

Flags: needinfo?(kershaw)
Has Regression Range: --- → yes
Severity: normal → S3

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.