Skip to content

feat: support cross-process interception via setupRemoteServer #2086

feat: support cross-process interception via setupRemoteServer

feat: support cross-process interception via setupRemoteServer #2086

Triggered via pull request January 9, 2025 18:32
Status Failure
Total duration 6m 39s
Artifacts 1

ci.yml

on: pull_request
test (unit) (18)
48s
test (unit) (18)
test (node.js) (18)
55s
test (node.js) (18)
test (e2e) (18)
46s
test (e2e) (18)
test (browser)
5m 11s
test (browser)
test (react-native)
23s
test (react-native)
test (node.js) (20)
1m 4s
test (node.js) (20)
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Unhandled error: test/node/rest-api/response/body-stream.node.test.ts#L95
AssertionError: expected 478 to be greater than or equal to 490 ❯ IncomingMessage.<anonymous> test/node/rest-api/response/body-stream.node.test.ts:95:51 ❯ Object.onceWrapper node:events:632:28 ❯ IncomingMessage.emit node:events:530:35 ❯ endReadableNT node:internal/streams/readable:1698:12 ❯ processTicksAndRejections node:internal/process/task_queues:82:21 This error originated in "test/node/rest-api/response/body-stream.node.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports delays when enqueuing chunks". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
test (node.js) (20)
Process completed with exit code 1.
Unhandled error: test/node/rest-api/response/body-stream.node.test.ts#L95
AssertionError: expected 487 to be greater than or equal to 490 ❯ IncomingMessage.<anonymous> test/node/rest-api/response/body-stream.node.test.ts:95:51 ❯ Object.onceWrapper node:events:631:28 ❯ IncomingMessage.emit node:events:529:35 ❯ endReadableNT node:internal/streams/readable:1400:12 ❯ processTicksAndRejections node:internal/process/task_queues:82:21 This error originated in "test/node/rest-api/response/body-stream.node.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "supports delays when enqueuing chunks". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
test/node/msw-api/setup-remote-server/life-cycle-event-forwarding.node.test.ts > emits correct events for the request handled in the test process: test/node/msw-api/setup-remote-server/life-cycle-event-forwarding.node.test.ts#L48
AssertionError: expected [ …(4) ] to deeply equal [ …(4) ] - Expected + Received Array [ Array [ "[request:start] GET https://example.com/resource 36d8811572d02", ], Array [ - "[request:match] GET https://example.com/resource 36d8811572d02", + "[request:end] GET https://example.com/resource 36d8811572d02", ], Array [ - "[request:end] GET https://example.com/resource 36d8811572d02", + "[request:match] GET https://example.com/resource 36d8811572d02", ], Array [ "[response:mocked] GET https://example.com/resource 36d8811572d02 200 {\"mocked\":true}", ], ] ❯ test/node/msw-api/setup-remote-server/life-cycle-event-forwarding.node.test.ts:48:35
test (node.js) (18)
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size
playwright-report
47.8 KB