Skip to content

PR CHECK #5904 - 309220 celery queues #4856

PR CHECK #5904 - 309220 celery queues

PR CHECK #5904 - 309220 celery queues #4856

Triggered via pull request April 15, 2026 07:10
Status Cancelled
Total duration 15s
Artifacts

ci-pr.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 4 warnings
pragma / block-pragma
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
pragma / block-pragma
The operation was canceled.
mypy / mypy
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
tests / Selenium tests
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
mypy / mypy
The operation was canceled.
tests / Selenium tests
A task was canceled.
lint / lint
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
lint / lint
The operation was canceled.
frontend / checks
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
frontend / checks
The operation was canceled.
build / Build and Push
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
build / Build and Push
The operation was canceled.
tests / Unit tests
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
tests / Unit tests
Process completed with exit code 127.
tests / Unit tests
The operation was canceled.
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
CI-PR
Canceling since a higher priority waiting request for CI-PR-refs/pull/5904/merge exists
pragma / block-pragma
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
mypy / mypy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
lint / lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. 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/
tests / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/