Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

The job has exceeded the maximum execution time of 6h0m0s

The operation was canceled.

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/

Docker pull failed with exit code 1, back off 3.567 seconds before retry.

Docker pull failed with exit code 1, back off 5.452 seconds before retry.

Docker pull failed with exit code 1, back off 5.983 seconds before retry.

Docker pull failed with exit code 1, back off 3.643 seconds before retry.

Docker pull failed with exit code 1, back off 1.447 seconds before retry.

Docker pull failed with exit code 1, back off 7.807 seconds before retry.

Docker pull failed with exit code 1, back off 8.623 seconds before retry.

Docker pull failed with exit code 1, back off 6.287 seconds before retry.

Docker pull failed with exit code 1, back off 8.34 seconds before retry.

Docker pull failed with exit code 1, back off 5.163 seconds before retry.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. 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/

warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.

ERROR: 'conda activate "addons-ci"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: addons-ci You can list all discoverable environments with `conda info --envs`.

The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.