Skip to content

v2 WebRTC Calling Tests #11452

v2 WebRTC Calling Tests

v2 WebRTC Calling Tests #11452

Triggered via schedule December 25, 2024 17:00
Status Failure
Total duration 11m 44s
Artifacts

v2-webrtc-calling.yml

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

Annotations

4 errors, 25 warnings, and 8 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:192:7 › v2WebrtcFromRestTwoJoinAudioVideo › should handle a call from REST API to v2 clients: internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts#L264
1) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:192:7 › v2WebrtcFromRestTwoJoinAudioVideo › should handle a call from REST API to v2 clients, dialing both into a Conference at answer, audio/video Error: Timed out 10000ms waiting for expect(received).toContainText(expected) Expected string: "-> active" Received string: "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" Call log: - expect.toContainText with timeout 10000ms - waiting for locator('#callStatus') - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">…</span> - unexpected value "new -> ringing Early Media:false Answered: false" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" - locator resolved to <span id="callStatus">…</span> - unexpected value "hangup -> destroy Code:16 Reason: NORMAL_CLEARING" 262 | const callStatusCallee2 = pageCallee2.locator('#callStatus') 263 | expect(callStatusCallee2).not.toBe(null) > 264 | await expect(callStatusCallee2).toContainText('-> active') | ^ 265 | 266 | console.log('The call is active at ', new Date()) 267 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:264:37
determine_regions
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run E2E tests (us, production, PRODUCTION_E2E_JS_SW_TEST_CONFIG)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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 25.5s
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 33.0s
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 32.7s
Run E2E tests (me, production-me, PRODUCTION_E2E_JS_MEREGION_SW_TEST_CONFIG)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.7m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 27.0s
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.5m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 37.5s
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.6s
Run E2E tests (euswcom, production-euswcom, PRODUCTION_EUSWCOM_E2E_JS_SW_TEST_CONFIG)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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 29.3s
Run E2E tests (staging, staging, STAGING_E2E_JS_SW_TEST_CONFIG)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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 28.4s
🎭 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
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.5m)
🎭 Playwright Run Summary
7 passed (3.1m)
🎭 Playwright Run Summary
1 failed [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:192:7 › v2WebrtcFromRestTwoJoinAudioVideo › should handle a call from REST API to v2 clients, dialing both into a Conference at answer, audio/video 6 passed (3.2m)
🎭 Playwright Run Summary
7 passed (3.7m)
🎭 Playwright Run Summary
7 passed (3.3m)
🎭 Playwright Run Summary
7 passed (3.2m)