fix(runtime): display proper error when throwing in event handlers #75770
bartlomiejuci.yml
on: pull_request
pre-build
9s
Matrix: lint
bench release linux-x86_64
6s
build libs debug linux-x86_64
1m 57s
deno_core test linux-x86_64
11m 57s
deno_core miri linux-x86_64
5m 35s
Matrix: test-debug-linux-aarch64
Matrix: test-debug-macos-aarch64
Matrix: test-debug-windows-x86_64
Matrix: test-release-linux-x86_64
Matrix: test-debug-linux-x86_64
Matrix: test-debug-macos-x86_64
Matrix: test-debug-windows-aarch64
Matrix: test-release-linux-aarch64
Matrix: test-release-macos-aarch64
Matrix: test-release-macos-x86_64
Matrix: test-release-windows-aarch64
Matrix: test-release-windows-x86_64
publish canary
ci status
5s
Annotations
32 errors and 40 warnings
|
test unit debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test unit debug macos-x86_64
The operation was canceled.
|
|
test libs debug windows-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test libs debug windows-x86_64
The operation was canceled.
|
|
test specs (2/2) debug windows-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test specs (2/2) debug windows-x86_64
The operation was canceled.
|
|
test specs (1/2) debug windows-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test specs (1/2) debug windows-x86_64
The operation was canceled.
|
|
test integration (1/2) debug windows-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test integration (1/2) debug windows-x86_64
The operation was canceled.
|
|
build debug windows-aarch64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
build debug windows-aarch64
The operation was canceled.
|
|
test integration (2/2) debug windows-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test integration (2/2) debug windows-x86_64
The operation was canceled.
|
|
build debug linux-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
build debug linux-x86_64
The operation was canceled.
|
|
build release linux-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
build release linux-x86_64
The operation was canceled.
|
|
test integration (2/2) debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test integration (2/2) debug macos-x86_64
The operation was canceled.
|
|
test unit_node debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test unit_node debug macos-x86_64
The operation was canceled.
|
|
test specs (1/2) debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test specs (1/2) debug macos-x86_64
The operation was canceled.
|
|
test node_compat debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test node_compat debug macos-x86_64
The operation was canceled.
|
|
test specs (2/2) debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test specs (2/2) debug macos-x86_64
The operation was canceled.
|
|
test integration (1/2) debug macos-x86_64
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
test integration (1/2) debug macos-x86_64
The operation was canceled.
|
|
ci status
Process completed with exit code 1.
|
|
ci
Canceling since a higher priority waiting request for ci-fix/unload-event-error-display exists
|
|
pre-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build libs debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
lint debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit_node debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
lint debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test node_compat debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test node_compat debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
lint debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test libs debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (2/2) debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (1/2) debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (2/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (1/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (2/2) debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (1/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (2/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (1/2) debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit_node debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
deno_core test linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test node_compat debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test libs debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (2/2) debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (1/2) debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (1/2) debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (2/2) debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build release linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (2/2) debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test unit_node debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (1/2) debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test node_compat debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test specs (2/2) debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
test integration (1/2) debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
debug-linux-aarch64-deno
|
118 MB |
sha256:aad79ea33bdb5b0a5303a5a34b55290ec74be0b0b5db240091498d5421be6cde
|
|
|
debug-linux-aarch64-denort
|
73 MB |
sha256:dd6e82eeaca0cd1eb6d11c9c3ae928d8d2be63774fa721f353c794830cd7eced
|
|
|
debug-linux-aarch64-test-server
|
9.27 MB |
sha256:867342c6db8f6e3d30c9c6d736650e64a3c744fa05868569f9ebd2239b7e288f
|
|
|
debug-macos-aarch64-deno
|
108 MB |
sha256:26cd21cf6cd2d246db56c3311766e47eb8a8c8fee689e37efb11fb06f12971b3
|
|
|
debug-macos-aarch64-denort
|
66.8 MB |
sha256:b5eeb838c4d5988df7665a1fc2fc1dc393c2e7ef34d19c31cfb88bae98594584
|
|
|
debug-macos-aarch64-test-server
|
9.73 MB |
sha256:a40d5060a7fc9c1005b61a0600ed003a15733a9ce7ae5a7921696341e2bde60b
|
|
|
debug-macos-x86_64-deno
|
104 MB |
sha256:b05e24ec249f391288ff93d6f6b2f571ff99a9c146de7e7ae68205c62193f4f6
|
|
|
debug-macos-x86_64-denort
|
64.7 MB |
sha256:23388b588d3a135f0a29b24acb2054dba023fdb0f69c2fdc0956ea17b81b12cf
|
|
|
debug-macos-x86_64-test-server
|
9.26 MB |
sha256:0565e213d9c52b713d2d621d1ca02538e9dace0c7fc9de6696affc466a7e918d
|
|
|
debug-windows-x86_64-deno
|
82.5 MB |
sha256:dda166b2523b3efc47fcf6bd0c03d89057a2e2ec17d1ab7336a9e7167220290a
|
|
|
debug-windows-x86_64-denort
|
55.4 MB |
sha256:4e62218a2dd8d8147ecdd9f5f1aa23d1159efcbe1192ca9553b7b89bc09dc18f
|
|
|
debug-windows-x86_64-test-server
|
6.45 MB |
sha256:a8447580a8dc882c68083154594f1ae50da61ed70adee74fe83009e7645f7536
|
|
|
test-results-linux-aarch64-debug-integration-shard-0.json
|
8.42 KB |
sha256:72a4a0df9785e175fdaadf6b17978ee7c2bdfe3d68a10f88ff8131716f8330d8
|
|
|
test-results-linux-aarch64-debug-integration-shard-1.json
|
8.41 KB |
sha256:e875881d78c6e6cb066ff417df75b308f5f479b6a3318730667019d5229ecb79
|
|
|
test-results-linux-aarch64-debug-node_compat.json
|
30.8 KB |
sha256:52ab85a3916131210788ab55232f7b6eda0157307ef1068d76e30c2430bc039e
|
|
|
test-results-linux-aarch64-debug-specs-shard-0.json
|
19.1 KB |
sha256:b144477d946adc72ad7ba3426f30015b32eafbf6f5d30b730f8020fbda0d0f40
|
|
|
test-results-linux-aarch64-debug-specs-shard-1.json
|
19 KB |
sha256:13512fe3e8658280bb817f595c18dc140ba04bca468431785896f9248297c9c4
|
|
|
test-results-linux-aarch64-debug-unit.json
|
1.47 KB |
sha256:af4cb41ddc9fab92eaccbc861be1ff1353453f2658e5b402dbacd5d71e4f0eed
|
|
|
test-results-linux-aarch64-debug-unit_node.json
|
1.3 KB |
sha256:3af56b050db78a04a77b06644a5735b950987cba63b4f3042ebc46e1bc867990
|
|
|
test-results-macos-aarch64-debug-integration-shard-0.json
|
8.41 KB |
sha256:90448223e399c01bcb728f13bddc3705d86ae4563347e3369eb02f40c11b2282
|
|
|
test-results-macos-aarch64-debug-integration-shard-1.json
|
8.36 KB |
sha256:87a10592870ed9842848d000c5d0899e670e1435ea231b3e21f3d17092bda718
|
|
|
test-results-macos-aarch64-debug-node_compat.json
|
30.3 KB |
sha256:29a06a6f50fee1affd7918e0a3f262b319c13d1b37377d6299cdc2b55c42d431
|
|
|
test-results-macos-aarch64-debug-specs-shard-0.json
|
19.2 KB |
sha256:d495f113fa4bcc632625fe0cec84cf6c1c078f0d72b7a05e995de8e1d3b35b2a
|
|
|
test-results-macos-aarch64-debug-specs-shard-1.json
|
18.9 KB |
sha256:bf2e6f3533cccc488266abbf9f4657abf40c1056ce9a8d89ded0294aef48cd21
|
|
|
test-results-macos-aarch64-debug-unit.json
|
1.48 KB |
sha256:3bc00adcfca67cab6a578a738d6718d40584ab538231f4cda8ed81ba7f71ff6d
|
|
|
test-results-macos-aarch64-debug-unit_node.json
|
1.29 KB |
sha256:00d2b4e5311495628d96e98887c8bf7fb6f960826d3da468ed09a257c385d671
|
|
|
test-results-macos-x86_64-debug-integration-shard-0.json
|
14.7 KB |
sha256:b1ec20573b049e635e6ae2e3dd23bda22018a098a87dc212d8e1085d4f47ad16
|
|
|
test-results-macos-x86_64-debug-integration-shard-1.json
|
696 Bytes |
sha256:a8f97d98caf866a5b3f7cd3f8ece98bb4d55e619055f4dff7673be823eb72b90
|
|
|
test-results-macos-x86_64-debug-node_compat.json
|
741 Bytes |
sha256:f404bb733da3d294644a4be3d8b2202a5000bd1f7afdc3d534ca44f0912f7c80
|
|
|
test-results-macos-x86_64-debug-specs-shard-0.json
|
33.4 KB |
sha256:ed7308b99ce87760f257d44869616c70103c967cef03dd6e14bb4a3e1b37784f
|
|
|
test-results-macos-x86_64-debug-specs-shard-1.json
|
33.4 KB |
sha256:ed7308b99ce87760f257d44869616c70103c967cef03dd6e14bb4a3e1b37784f
|
|
|
test-results-macos-x86_64-debug-unit.json
|
1.52 KB |
sha256:57e8de89dab821d77ef4db45087a4e466eedb17cecc0b6bed588a6a04bf5c85e
|
|
|
test-results-macos-x86_64-debug-unit_node.json
|
1.33 KB |
sha256:140d8a57643fa25743c5a117f8b551e0f616d639ff495fb47aa8451f051ee9e8
|
|
|
test-results-windows-x86_64-debug-integration-shard-0.json
|
655 Bytes |
sha256:4495e865d387e67c51c8cb7c44837e258b0a08aa9573b61124f40d1b2dd26fbf
|
|
|
test-results-windows-x86_64-debug-integration-shard-1.json
|
670 Bytes |
sha256:de8a4de38b3620a8dc44d80066c0a2402450da359fdacbc9103c06e752d0da59
|
|
|
test-results-windows-x86_64-debug-node_compat.json
|
27.7 KB |
sha256:5e7b077aa5b5b7355ed4b852475965cb01282312cf7f0a6cf8f1eb0e8739626a
|
|
|
test-results-windows-x86_64-debug-specs-shard-0.json
|
34.2 KB |
sha256:0e9dc1bde4779bbc94ed12b801b2c6730f2b1a19d560735e1aaba040c20aee67
|
|
|
test-results-windows-x86_64-debug-specs-shard-1.json
|
34.2 KB |
sha256:0e9dc1bde4779bbc94ed12b801b2c6730f2b1a19d560735e1aaba040c20aee67
|
|
|
test-results-windows-x86_64-debug-unit.json
|
1.51 KB |
sha256:a878b88f806e27b4c729403ae990799475e1f21ed27e7297b51bcc99582e7cc7
|
|
|
test-results-windows-x86_64-debug-unit_node.json
|
1.32 KB |
sha256:192ce0b5948d0814020dd0dbc36f166fb72cba700c3f12df134527c63401d768
|
|