Skip to content

Unhandled promise rejections no longer kill the whole server if not i… #12827

Unhandled promise rejections no longer kill the whole server if not i…

Unhandled promise rejections no longer kill the whole server if not i… #12827

Triggered via push May 12, 2026 20:16
Status Failure
Total duration 41m 5s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
E2E Tests (Node 22.x, Freestyle mock)
Process completed with exit code 1.
tests/backend/endpoints/api/v1/auth/sessions/current/index.test.ts > should sign out users: apps/e2e/tests/helpers.ts#L254
StackAssertionError: Expected at least 1 messages with subject containing "Verify your email", but found 0 This is likely an error in Stack. Please make sure you are running the newest version and report it. ❯ Mailbox.waitForMessagesWithSubjectCount tests/helpers.ts:254:13 ❯ Mailbox.waitForMessagesWithSubject tests/helpers.ts:240:14 ❯ Object.signUpWithEmail tests/backend/backend-helpers.ts:586:9 ❯ tests/backend/endpoints/api/v1/auth/sessions/current/index.test.ts:5:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { extraData: { messages: [] }, customCaptureExtraArgs: [ { messages: [] } ] }
tests/backend/endpoints/api/v1/auth/password/sign-up.test.ts > should not allow signing up with an e-mail that already exists: apps/e2e/tests/helpers.ts#L254
StackAssertionError: Expected at least 1 messages with subject containing "Verify your email", but found 0 This is likely an error in Stack. Please make sure you are running the newest version and report it. ❯ Mailbox.waitForMessagesWithSubjectCount tests/helpers.ts:254:13 ❯ Mailbox.waitForMessagesWithSubject tests/helpers.ts:240:14 ❯ Object.signUpWithEmail tests/backend/backend-helpers.ts:586:9 ❯ tests/backend/endpoints/api/v1/auth/password/sign-up.test.ts:128:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { extraData: { messages: [] }, customCaptureExtraArgs: [ { messages: [] } ] }
tests/backend/endpoints/api/v1/auth/passkey/sign-in.test.ts > should fail if passkey does not exist: apps/e2e/tests/helpers.ts#L254
StackAssertionError: Expected at least 1 messages with subject containing "Verify your email", but found 0 This is likely an error in Stack. Please make sure you are running the newest version and report it. ❯ Mailbox.waitForMessagesWithSubjectCount tests/helpers.ts:254:13 ❯ Mailbox.waitForMessagesWithSubject tests/helpers.ts:240:14 ❯ Object.signUpWithEmail tests/backend/backend-helpers.ts:586:9 ❯ tests/backend/endpoints/api/v1/auth/passkey/sign-in.test.ts:90:15 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { extraData: { messages: [] }, customCaptureExtraArgs: [ { messages: [] } ] }
E2E Tests (Node 22.x, Freestyle prod)
The strategy configuration was canceled because "build._22_x_mock" failed
E2E Tests (Node 22.x, Freestyle prod)
The operation was canceled.
E2E Tests (Node 22.x, Freestyle mock)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E Tests (Node 22.x, Freestyle prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/