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

Process completed with exit code 1.

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

Process completed with exit code 1.

1) [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:19:7 › v2WebrtcFromRestSilence › should handle a call from REST API to v2 client, playing silence at answer Error: Timed out 10000ms waiting for expect(received).toContainText(expected) Expected string: "-> active" Received string: "None" 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">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">None</span> - unexpected value "None" - locator resolved to <span id="callStatus">None</span> - unexpected value "None" 71 | const callStatusCallee = pageCallee.locator('#callStatus') 72 | expect(callStatusCallee).not.toBe(null) > 73 | await expect(callStatusCallee).toContainText('-> active') | ^ 74 | 75 | console.log('The call is active at ', new Date()) 76 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:73:36

Process completed with exit code 1.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.8m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 31.5s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.9m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 26.6s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.1m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 32.0s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.5m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 25.9s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.9m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 43.4s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 3.2m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.6s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.8m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 30.5s

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

internal/e2e-js/[v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts took 2.8m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 28.5s

7 passed (3.4m)

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)

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.7m)

1 failed [v2WebRTC] › v2Webrtc/v2WebrtcFromRest.spec.ts:19:7 › v2WebrtcFromRestSilence › should handle a call from REST API to v2 client, playing silence at answer 6 passed (2.9m)

7 passed (3.7m)

7 passed (3.8m)

7 passed (3.4m)