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).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" 155 | const callStatusCallee = pageCallee.locator('#callStatus') 156 | expect(callStatusCallee).not.toBe(null) > 157 | await expect(callStatusCallee).toContainText('-> active') | ^ 158 | 159 | console.log('The call is active at ', new Date()) 160 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:157:36

Process completed with exit code 1.

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).toContainText(expected) Expected string: "-> active" Received string: "new -> ringing Early Media:false Answered: false" 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">…</span> - unexpected value "new -> ringing Early Media:false Answered: false" 155 | const callStatusCallee = pageCallee.locator('#callStatus') 156 | expect(callStatusCallee).not.toBe(null) > 157 | await expect(callStatusCallee).toContainText('-> active') | ^ 158 | 159 | console.log('The call is active at ', new Date()) 160 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:157:36

Process completed with exit code 1.

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: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: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).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" 155 | const callStatusCallee = pageCallee.locator('#callStatus') 156 | expect(callStatusCallee).not.toBe(null) > 157 | await expect(callStatusCallee).toContainText('-> active') | ^ 158 | 159 | console.log('The call is active at ', new Date()) 160 | at /home/runner/work/signalwire-js/signalwire-js/internal/e2e-js/tests/v2Webrtc/v2WebrtcFromRest.spec.ts:157: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.1m

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

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

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 31.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 33.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 26.7s

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

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 35.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 2.4m

internal/e2e-js/[v2WebRTC] › v2Webrtc/webrtcCalling.spec.ts took 38.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 29.3s

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 29.1s

1 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 6 passed (2.6m)

1 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 6 passed (2.9m)

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)

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)

7 passed (3.6m)

1 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 6 passed (3.1m)

7 passed (3.3m)