Update numpy #3
camdecosterci.yml
on: push
install-and-cibuild
32s
publish-dist
2m 13s
publish-dist-node-v22
2m 7s
test-stackgl-bundle
30s
test-topojson-build
Matrix: make-baselines-b64
Matrix: make-baselines-virtual-webgl
Matrix: make-baselines
timezone-jasmine
39s
flaky-no-gl-jasmine
1m 2s
bundle-jasmine
1m 24s
mathjax-firefoxLatest
1m 3s
noci-jasmine
1m 11s
mock-validation
6m 31s
source-syntax
42s
Matrix: no-gl-jasmine
Matrix: virtual-webgl-jasmine
Matrix: webgl-jasmine-chromeLatest
Matrix: webgl-jasmine
test-baselines-b64
0s
test-baselines-virtual-webgl
test-baselines
test-baselines-mathjax3
test-exports
Annotations
40 errors and 33 warnings
|
timezone-jasmine
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
make-baselines-mathjax3
Process completed with exit code 1.
|
|
virtual-webgl-jasmine (6)
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
webgl-jasmine (6)
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
make-exports
Process completed with exit code 1.
|
|
no-gl-jasmine (2)
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
make-baselines (8)
Process completed with exit code 1.
|
|
make-baselines (7)
Process completed with exit code 1.
|
|
make-baselines-b64 (1)
Process completed with exit code 1.
|
|
make-baselines (9)
Process completed with exit code 1.
|
|
make-baselines (0)
Process completed with exit code 1.
|
|
make-baselines-b64 (0)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (2)
Process completed with exit code 1.
|
|
make-baselines-b64 (5)
Process completed with exit code 1.
|
|
make-baselines-b64 (2)
Process completed with exit code 1.
|
|
make-baselines (5)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (0)
Process completed with exit code 1.
|
|
make-baselines-b64 (3)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (7)
Process completed with exit code 1.
|
|
make-baselines (6)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (4)
Process completed with exit code 1.
|
|
make-baselines (11)
Process completed with exit code 1.
|
|
make-baselines (10)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (3)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (5)
Process completed with exit code 1.
|
|
make-baselines (1)
Process completed with exit code 1.
|
|
make-baselines (2)
Process completed with exit code 1.
|
|
make-baselines-b64 (4)
Process completed with exit code 1.
|
|
make-baselines (4)
Process completed with exit code 1.
|
|
make-baselines-b64 (8)
Process completed with exit code 1.
|
|
make-baselines-b64 (7)
Process completed with exit code 1.
|
|
make-baselines-b64 (9)
Process completed with exit code 1.
|
|
make-baselines-b64 (11)
Process completed with exit code 1.
|
|
make-baselines (3)
Process completed with exit code 1.
|
|
make-baselines-b64 (10)
Process completed with exit code 1.
|
|
make-baselines-virtual-webgl (1)
Process completed with exit code 1.
|
|
make-baselines-b64 (6)
Process completed with exit code 1.
|
|
no-gl-jasmine (1)
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
make-baselines-virtual-webgl (6)
Process completed with exit code 1.
|
|
no-gl-jasmine (3)
The process '/usr/bin/xvfb-run' failed with exit code 1
|
|
timezone-jasmine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
flaky-no-gl-jasmine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
mathjax-firefoxLatest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
noci-jasmine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
bundle-jasmine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine-chromeLatest (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
virtual-webgl-jasmine (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
no-gl-jasmine (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
webgl-jasmine (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
no-gl-jasmine (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
no-gl-jasmine (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
|
no-gl-jasmine (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: coactions/setup-xvfb@v1. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-output
|
3.4 MB |
sha256:bef2f997470c763f2867c5b226a4d419137b76f9ccc38785415f69511fc52a79
|
|
|
dist-node18
|
20.3 MB |
sha256:2417cd36c2b72bd47885d51c5f3a58ff92bbe1707afb4e59eeae21814b43eb06
|
|
|
dist-node22
|
20.3 MB |
sha256:f076f07f53de00570a2dd50b1e268f802b7cb5b4c78aa680521229f5a4a5b29a
|
|
|
tarball-node18
|
32.8 MB |
sha256:bebb1e39c2fdce683bbd772194d31333bfdfd0952e67fc223b1dd1c5c29c08e0
|
|
|
tarball-node22
|
32.8 MB |
sha256:9fe2632f75f03daf98876c5b5b1a2fce5eabb0a891366755cce02ccd4914108a
|
|