Skip to content

build(deps): bump tornado from 6.5.4 to 6.5.5 #4158

build(deps): bump tornado from 6.5.4 to 6.5.5

build(deps): bump tornado from 6.5.4 to 6.5.5 #4158

Triggered via pull request March 12, 2026 00:45
Status Failure
Total duration 13m 24s
Artifacts 12

docker-images.yml

on: pull_request
Matrix: build
Matrix: merge
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 12 warnings
build (restapi, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/restapi: denied: installation not allowed to Write organization package
build (mlflow-tracking, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/mlflow-tracking: denied: installation not allowed to Write organization package
build (tensorflow2-cpu, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/tensorflow2-cpu: denied: installation not allowed to Write organization package
build (nginx, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/nginx: denied: installation not allowed to Write organization package
build (pytorch-cpu, linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/pytorch-cpu: denied: installation not allowed to Write organization package
build (nginx, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/nginx: denied: installation not allowed to Write organization package
build (mlflow-tracking, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/mlflow-tracking: denied: installation not allowed to Write organization package
build (pytorch-cpu, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/pytorch-cpu: denied: installation not allowed to Write organization package
build (restapi, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/restapi: denied: installation not allowed to Write organization package
build (tensorflow2-cpu, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/tensorflow2-cpu: denied: installation not allowed to Write organization package
build (tensorflow2-gpu, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/tensorflow2-gpu: denied: installation not allowed to Write organization package
build (pytorch-gpu, linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: failed to push ghcr.io/usnistgov/dioptra/pytorch-gpu: denied: installation not allowed to Write organization package
build (restapi, linux/arm64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (mlflow-tracking, linux/arm64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (tensorflow2-cpu, linux/arm64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (nginx, linux/arm64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (pytorch-cpu, linux/arm64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (nginx, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (mlflow-tracking, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (pytorch-cpu, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (restapi, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (tensorflow2-cpu, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (tensorflow2-gpu, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (pytorch-gpu, linux/amd64)
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@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
usnistgov~dioptra~29415X.dockerbuild Expired
97.6 KB
sha256:8c100b0b8279bdce102362cb9eb03186822b014857852065b25ba3715616dc09
usnistgov~dioptra~3TSEEP.dockerbuild Expired
88.8 KB
sha256:3ded5efc392b1c87b3ddf53bede011cc26a7cd5fa78ab10c2078581f337a64c5
usnistgov~dioptra~40WVKU.dockerbuild Expired
98 KB
sha256:eacf239efd84765e89c5107a7a4482e74c99a1a4440a5d1e4bdbf07a83e81133
usnistgov~dioptra~AQH17Z.dockerbuild Expired
122 KB
sha256:d7f7e16de2785bbf0680159d889b189cff68d7e9e1bd4e217dae0b57d60164f5
usnistgov~dioptra~BDZQT7.dockerbuild Expired
103 KB
sha256:bce6d7c019031eba105dd82dac63cf8410102b9e211f66460d7389378dd01ddf
usnistgov~dioptra~F4RT40.dockerbuild Expired
97.6 KB
sha256:ca1244838ac6197ebf48ead1376237cc334e752c74c63f27dd2785338e756b62
usnistgov~dioptra~KHTN94.dockerbuild Expired
98.1 KB
sha256:6c9bf348a30a242917851259d1eb45a98bc56406e834cf43fcc00c495b388bab
usnistgov~dioptra~LQTZUL.dockerbuild Expired
68.7 KB
sha256:e51db1f129de57b45333e8c0a3498b1f5a4df6575828b951cd0ddd19b8ae7e7b
usnistgov~dioptra~OU1NHW.dockerbuild Expired
66.5 KB
sha256:63e523e5bf331ed11a529ead8f39202a24ee65db25ae49b276c5bfe89631f28b
usnistgov~dioptra~PFZK40.dockerbuild Expired
88 KB
sha256:9f187ac9e9ad970072d1781225b5c777c22959590262db94e3539c3b0be0a094
usnistgov~dioptra~Q1N4ZD.dockerbuild Expired
119 KB
sha256:db253ae541d34e8f4dc9a78a65af588f485919a3731baf9629212337f864eff2
usnistgov~dioptra~WLFJOH.dockerbuild Expired
93.6 KB
sha256:82c638dbcc6a8aee310b85f96feed997bd6d117b36701c9f196e6c3368819cb4