Skip to content

relock w/ conda-lock (#5870) #10099

relock w/ conda-lock (#5870)

relock w/ conda-lock (#5870) #10099

Triggered via push March 30, 2026 20:10
Status Failure
Total duration 15m 2s
Artifacts 6

tests.yml

on: push
Check if we can skip the merge queue
14s
Check if we can skip the merge queue
Matrix: tests / tests-mongodb
Matrix: tests / tests
tests  /  test-coverage-and-durations
0s
tests / test-coverage-and-durations
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
tests / tests (2)
buildx failed with: ERROR: failed to build: failed to solve: failed to compute cache key: failed to copy: httpReadSeeker: failed open: unexpected status from GET request to https://quay.io/v2/condaforge/linux-anvil-cos7-x86_64/blobs/sha256:a84c72f52b9653402e555f0c197f4d6cccfc78c74875032aa7bfb65853c5e251: 502 Bad Gateway
tests / status
Process completed with exit code 1.
Check if we can skip the merge queue
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/github-script@v7. 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 / tests (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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 / tests-mongodb (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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 / tests (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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
coverage-1
17 KB
sha256:5a372fa358613b0554976115aaee71bd86d32a07aaeea4d24bc5bb3e8d8ad940
coverage-mongodb
14 KB
sha256:3d913296d0578f47c0625b30660521009e3bbb98a6ffb3760402b3cf47497246
regro~cf-scripts~IE6GRX.dockerbuild
49.3 KB
sha256:137f628ddb383be9ae037bbb6011cb5645e5c80b05be9a6eacbcb9542a3b8bd3
regro~cf-scripts~LM73JV.dockerbuild
25.6 KB
sha256:2405352a78c281e56d4762c035c2167b6c15c832b3da8c2ed6477ec9578953a9
test-durations-1
16.9 KB
sha256:c748d09211232bfc91e0f03cd5953f64c11277c3f690a7db54d8058d747ff533
test-durations-mongodb
391 Bytes
sha256:dd9566c05658db5db81d96669201140a2a77e7647b83b0502aa63889f877af1a