Open Bug 1017324 Opened 11 years ago Updated 3 years ago

Get data channel tests working on steeplechase

Categories

(Core :: WebRTC: Networking, defect, P4)

Product:
Core
Component:
WebRTC: Networking
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: drno, Unassigned)

Details

(Whiteboard: [webrtc-mochitest],[steeplechase])

Our current test_dataChannel_* tests have these steps: SEND_MESSAGE, SEND_BLOB, CREATE_SECOND_DATA_CHANNEL, SEND_MESSAGE_THROUGH_LAST_OPENED_CHANNEL, SEND_MESSAGE_THROUGH_FIRST_CHANNEL, CREATE_NEGOTIATED_DATA_CHANNEL, SEND_MESSAGE_THROUGH_LAST_OPENED_CHANNEL2 which all can not be filtered to one of the two machines in a steeplechase setup and even worse most of these steps rely on having access to pcLocal and pcRemote at the same time. They all need to be fixed before any test_dataChannel_* test can be executed properly in a steeplechase environment, which for example allows proper testing with TURN.
Target Milestone: --- → mozilla33
I think this can wait until Fx34. If we get it earlier, great.
Target Milestone: mozilla33 → mozilla34
Priority: -- → P2
Whiteboard: [webrtc-mochitest],[steeplechase]
backlog: --- → webRTC+
Rank: 35
Priority: P2 → P3
Target Milestone: mozilla34 → ---
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.