Skip to content

feat(storage): introduce storage refactoring proposal to reduce globa… #12206

feat(storage): introduce storage refactoring proposal to reduce globa…

feat(storage): introduce storage refactoring proposal to reduce globa… #12206

Triggered via pull request April 3, 2026 17:01
Status Success
Total duration 19m 9s
Artifacts 6

cluster.yaml

on: pull_request
Stateless zot with minio and boltdb
19m 4s
Stateless zot with minio and boltdb
Stateless zot with minio and redis
17m 45s
Stateless zot with minio and redis
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Stateless zot with minio and redis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.21.0. 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/
Stateless zot with minio and redis
Could not find external JSON file for benchmark data at /home/runner/work/zot/zot/cache/benchmark-data.json. Using empty default: Error: ENOENT: no such file or directory, open '/home/runner/work/zot/zot/cache/benchmark-data.json'
Stateless zot with minio and boltdb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: benchmark-action/github-action-benchmark@v1.21.0. 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
logs-push-pull-bolt Expired
11.1 KB
sha256:b69442294fb8ddd71ffbcc9fe9a9fc5dd4c8c3376e5cf53e521b6abb46add387
logs-push-pull-redis Expired
11.6 KB
sha256:07c588bb92e91daec267927c7970523445a7fbcc61413a4c0b39b66dd8369b84
logs-src-cidr-bolt Expired
226 KB
sha256:c654b2322bd3dadd3d3988d33af3db2f57b7f07bf0d82f7c8380d069e251b5a0
logs-src-cidr-redis Expired
226 KB
sha256:e25473f50aa235376d777c758a5e10d091b5aa4e3c59258f548fb7357cd2552e
logs-src-ips-bolt Expired
227 KB
sha256:779d9022ac2891384db036b5fe18c687d1781d02e873ac8e6d272a5d232382b2
logs-src-ips-redis Expired
227 KB
sha256:2d3e6fa492098aa9d8f9a254288ea4877f5bbcfa72363849b46792a48b14c8e4