Skip to content

v2 WebRTC Calling Tests #6772

v2 WebRTC Calling Tests

v2 WebRTC Calling Tests #6772

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

v2-webrtc-calling.yml

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

Annotations

2 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.
🎭 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.4m)
🎭 Playwright Run Summary
7 passed (3.4m)
🎭 Playwright Run Summary
7 passed (3.4m)
🎭 Playwright Run Summary
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.6m)
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 27.2s
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 32.6s
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 31.9s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 37.4s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 30.3s