Skip to content

v2 WebRTC Calling Tests #6779

v2 WebRTC Calling Tests

v2 WebRTC Calling Tests #6779

Triggered via schedule September 18, 2024 13:33
Status Failure
Total duration 20m 15s
Artifacts

v2-webrtc-calling.yml

on: schedule
determine_regions
0s
determine_regions
Matrix: Run E2E tests
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 10 warnings, and 5 notices
[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients: internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts#L402
1) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only Error: Timed out 10000ms waiting for expect(received).toContainText(expected) Expected string: "-> active" Received string: "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" Call log: - expect.toContainText with timeout 10000ms - waiting for locator('#callStatus') - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" 400 | 401 | await Promise.all([ > 402 | expect(callStatusCallee1).toContainText('-> active'), | ^ 403 | expect(callStatusCallee2).toContainText('-> active') 404 | ]) 405 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:402:33
Run E2E tests (us, production, PRODUCTION_E2E_JS_SW_TEST_CONFIG)
Process completed with exit code 1.
[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:106:7 › v2WebrtcFromRest › should handle a call from REST API to v2 client: internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts#L117
1) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:106:7 › v2WebrtcFromRest › should handle a call from REST API to v2 client, dialing into a Conference at answer Error: Timed out 10000ms waiting for expect(received).toBeEnabled() Call log: - expect.toBeEnabled with timeout 10000ms - waiting for locator('#hangupCall') - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" - locator resolved to <button disabled id="hangupCall" onclick="hangup()" clas…>Hang up</button> - unexpected value "disabled" 115 | 116 | // Expect the Hangup button to be enabled (call active) > 117 | await expect(hangupCall).toBeEnabled() | ^ 118 | *** 119 | 120 | const expectCallHangup = async (page: Page) => *** at expectCallActive (/home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:117:32) at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:166:11
[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients: internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts#L402
2) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only Error: Timed out 10000ms waiting for expect(received).toContainText(expected) Expected string: "-> active" Received string: "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" Call log: - expect.toContainText with timeout 10000ms - waiting for locator('#callStatus') - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" 400 | 401 | await Promise.all([ > 402 | expect(callStatusCallee1).toContainText('-> active'), | ^ 403 | expect(callStatusCallee2).toContainText('-> active') 404 | ]) 405 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:402:33
[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients: internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts#L403
1) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only Error: Timed out 10000ms waiting for expect(received).toContainText(expected) Expected string: "-> active" Received string: "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" Call log: - expect.toContainText with timeout 10000ms - waiting for locator('#callStatus') - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:804 Reason: MEDIA_TIMEOUT" 401 | await Promise.all([ 402 | expect(callStatusCallee1).toContainText('-> active'), > 403 | expect(callStatusCallee2).toContainText('-> active') | ^ 404 | ]) 405 | 406 | console.log('Time to check the audio energy at ', new Date()) at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:403:33
🎭 Playwright Run Summary
1 failed [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only 6 passed (3.3m)
🎭 Playwright Run Summary
2 failed [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:106:7 › v2WebrtcFromRest › should handle a call from REST API to v2 client, dialing into a Conference at answer [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only 5 passed (3.8m)
🎭 Playwright Run Summary
1 failed [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:309:7 › v2WebrtcFromRestTwoJoinAudioTURN › should handle a call from REST API to 2 v2 clients, dialing both into a Conference at answer, audio G711, TURN only 6 passed (3.7m)
🎭 Playwright Run Summary
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.4m)
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.8m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 26.0s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.2m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 31.9s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.1m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 33.8s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.9m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.5s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.9m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 29.4s