Skip to content

Run tests suite

Run tests suite #591

Triggered via schedule May 17, 2026 03:40
Status Failure
Total duration 1h 0m 17s
Artifacts

cron-run-tests.yaml

on: schedule
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 26 warnings
Test (3.13, ubuntu-24.04)
Final attempt failed. Child_process exited with error code 1
Test (3.13, ubuntu-24.04)
Process completed with exit code 1.
Test (3.11, ubuntu-22.04)
Final attempt failed. Child_process exited with error code 1
Test (3.11, ubuntu-22.04)
Process completed with exit code 1.
Test (3.12, ubuntu-22.04)
Final attempt failed. Child_process exited with error code 1
Test (3.12, ubuntu-22.04)
Process completed with exit code 1.
Test (3.14, ubuntu-22.04)
Final attempt failed. Child_process exited with error code 1
Test (3.14, ubuntu-22.04)
Process completed with exit code 1.
Test (3.11, ubuntu-24.04)
Final attempt failed. Child_process exited with error code 1
Test (3.11, ubuntu-24.04)
Process completed with exit code 1.
Test (3.12, ubuntu-24.04)
Final attempt failed. Child_process exited with error code 1
Test (3.12, ubuntu-24.04)
Process completed with exit code 1.
Test (3.14, ubuntu-24.04)
Final attempt failed. Child_process exited with error code 1
Test (3.14, ubuntu-24.04)
Process completed with exit code 1.
Test (3.14, windows-2022)
Final attempt failed. Child_process exited with error code 1
Test (3.14, windows-2022)
Process completed with exit code 1.
Test (3.11, windows-2022)
Final attempt failed. Child_process exited with error code 1
Test (3.11, windows-2022)
Process completed with exit code 1.
Test (3.12, windows-2022)
Final attempt failed. Child_process exited with error code 1
Test (3.12, windows-2022)
Process completed with exit code 1.
Test (3.13, windows-2022)
Final attempt failed. Child_process exited with error code 1
Test (3.13, windows-2022)
Process completed with exit code 1.
Test (3.13, ubuntu-22.04)
The job has exceeded the maximum execution time of 1h0m0s
Test (3.13, ubuntu-22.04)
The operation was canceled.
Test (3.10, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.10, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.10, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.13, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.13, ubuntu-24.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.11, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.11, ubuntu-22.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.12, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.12, ubuntu-22.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.14, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.14, ubuntu-22.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.11, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.11, ubuntu-24.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.12, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.12, ubuntu-24.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.14, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.14, ubuntu-24.04)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.14, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.14, windows-2022)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.11, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.11, windows-2022)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.12, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.12, windows-2022)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.13, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/
Test (3.13, windows-2022)
Attempt 1 failed. Reason: Child_process exited with error code 1
Test (3.13, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: oprypin/find-latest-tag@dd2729fe78b0bb55523ae2b2a310c6773a652bd1. 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/