Skip to content
v2 WebRTC Calling Tests

v2 WebRTC Calling Tests #11471

Sign in to view logs

v2 WebRTC Calling Tests

v2 WebRTC Calling Tests #11471

Triggered via schedule December 26, 2024 03:04
@ryanwiryanwi
⁠ ee3728e
main
Status Failure
Total duration 12m 18s
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, 25 warnings, and 8 notices
[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#L203
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).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" 201 | 202 | // Expect the Hangup button to be enabled (call active) > 203 | await expect(hangupCall).toBeEnabled() | ^ 204 | *** 205 | 206 | const expectCallHangup = async (page: Page) => *** at expectCallActive (/home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:203:32) at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:274:7
Run E2E tests (eu, production-eu, PRODUCTION_E2E_JS_EUREGION_SW_TEST_CONFIG, region="eu")
Process completed with exit code 1.
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.7m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 26.4s
Run E2E tests (ch, production-ch, PRODUCTION_E2E_JS_CHREGION_SW_TEST_CONFIG, region="eu")
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 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 33.2s
Run E2E tests (eu, production-eu, PRODUCTION_E2E_JS_EUREGION_SW_TEST_CONFIG, region="eu")
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 3.1m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 32.1s
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 26.4s
Run E2E tests (spr-preprod, production-spr-preprod, PRODUCTION_E2E_JS_SPRPREPRODREGION_SW_TEST_CO...
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 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.6s
Run E2E tests (spr-prod, production-spr-prod, PRODUCTION_E2E_JS_SPRPRODREGION_SW_TEST_CONFIG, reg...
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 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.5s
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 3.0m
Slow Test: internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts#L1
internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.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 29.1s
🎭 Playwright Run Summary
7 passed (3.1m)
🎭 Playwright Run Summary
7 passed (3.5m)
🎭 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.6m)
🎭 Playwright Run Summary
7 passed (3.2m)
🎭 Playwright Run Summary
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.6m)
🎭 Playwright Run Summary
7 passed (3.3m)