Skip to content
ci

feat: treat unhandled exceptions in handlers as 500 error responses #1649

Sign in to view logs

feat: treat unhandled exceptions in handlers as 500 error responses

feat: treat unhandled exceptions in handlers as 500 error responses #1649

Triggered via pull request April 21, 2024 09:13
@kettanaitokettanaito
synchronize #2135
fix/interceptors-node-condition
Status Failure
Total duration 5m 9s
Artifacts –

ci.yml

on: pull_request
build
2m 23s
build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts > errors on unhandled request when using the "error" value: test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts#L71
AssertionError: expected 'Must not resolve' to be 'Failed to fetch' // Object.is equality - Expected + Received - Failed to fetch + Must not resolve ❯ test/node/msw-api/setup-server/scenarios/on-unhandled-request/error.node.test.ts:71:32
build
Process completed with exit code 1.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, pnpm/action-setup@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build
No files were found with the provided path: test/browser/test-results. No artifacts will be uploaded.