Skip to content

fix(seer): Make Seer repo preferences cleanup synchronous to prevent stale dual-writes #250073

fix(seer): Make Seer repo preferences cleanup synchronous to prevent stale dual-writes

fix(seer): Make Seer repo preferences cleanup synchronous to prevent stale dual-writes #250073

Triggered via pull request April 14, 2026 18:10
Status Cancelled
Total duration 45s
Artifacts

backend.yml

on: pull_request
detect what files changed
14s
detect what files changed
select tests
13s
select tests
api docs test
16s
api docs test
backend migration tests
13s
backend migration tests
cli test
18s
cli test
requirements check
requirements check
check migration
15s
check migration
monolith-dbs test
16s
monolith-dbs test
backend typing
15s
backend typing
api url typescript generation
api url typescript generation
calculate test shards
0s
calculate test shards
Matrix: backend test
Backend
3s
Backend
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 8 warnings
backend migration tests
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
backend migration tests
The operation was canceled.
select tests
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
select tests
The operation was canceled.
backend typing
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
backend typing
The operation was canceled.
check migration
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
check migration
The operation was canceled.
monolith-dbs test
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
monolith-dbs test
The operation was canceled.
api docs test
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
api docs test
The operation was canceled.
cli test
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
cli test
The operation was canceled.
Backend
Process completed with exit code 1.
backend
Canceling since a higher priority waiting request for backend-srest2021/fix-disabled-repo exists
detect what files changed
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, dorny/paths-filter@0bc4621a3135347011ad047f9ecf449bf72ce2bd. 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/
backend migration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/
select tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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/
backend typing
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/
check migration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/
monolith-dbs test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/
api docs test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-node@1e60f620b9541d16bece96c5465dc8ee9832be0b, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/
cli test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546. 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/