Skip to content

arsenal bump

arsenal bump #755

Triggered via push March 14, 2025 10:21
Status Failure
Total duration 4m 35s
Artifacts 3

tests.yaml

on: push
build-ci  /  ...  /  build
24s
build-ci / warp10-ci / build
build-ci  /  vault-ci
25s
build-ci / vault-ci
build-ci  /  ...  /  build
27s
build-ci / redis-ci / build
build-ci  /  ...  /  build
16s
build-ci / redis-replica-ci / build
tests-v2-with-vault
3m 26s
tests-v2-with-vault
Matrix: tests-v1
Matrix: tests-v2-without-sensision
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 36 warnings
lint
Process completed with exit code 1.
run unit tests
Process completed with exit code 1.
run v1 client tests
Process completed with exit code 1.
run v1 cron tests
Process completed with exit code 1.
run v2 soft limit test
Process completed with exit code 1.
run v1 interval tests
Process completed with exit code 1.
run v2 hard limit test
Process completed with exit code 1.
run v1 server tests
Process completed with exit code 1.
tests-v2-with-vault
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L26
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
The 'as' keyword should match the case of the 'from' keyword: images/warp10/Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L23
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L25
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L27
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L30
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L3
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/warp10/Dockerfile#L31
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
build-ci / vault-ci
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Legacy key/value format with whitespace separator should not be used: images/redis/Dockerfile#L3
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/redis/Dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: images/redis/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: images/redis/Dockerfile#L17
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: .github/docker/redis-replica/Dockerfile#L7
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: .github/docker/redis-replica/Dockerfile#L8
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: .github/docker/redis-replica/Dockerfile#L9
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: .github/docker/redis-replica/Dockerfile#L12
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
lint
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run unit tests
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run unit tests
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v1 client tests
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v1 client tests
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v1 cron tests
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v1 cron tests
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v2 soft limit test
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v2 soft limit test
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v1 interval tests
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v1 interval tests
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v2 hard limit test
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v2 hard limit test
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
run v1 server tests
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip
run v1 server tests
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
tests-v2-with-vault
Cache not found for keys: node-cache-Linux-x64-yarn-3fc4c51892e0941485058fc97f980caea86238acf91bcfdbbff1ed570ce07ea8
tests-v2-with-vault
Cache not found for keys: setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-22.04-Ubuntu-python-3.9.21-pip

Artifacts

Produced during runtime
Name Size Digest
scality~utapi~3G7XK2.dockerbuild Expired
28.2 KB
sha256:3ecbb428bbd918dd8aa1c25832c0a58b08d1e98025fc266e633891be62a902ce
scality~utapi~UICRCK.dockerbuild Expired
46.3 KB
sha256:7c446caecf4d4b4e704a319e98911cc15c0f67e5a3d4cbf700cd735e9c7a2155
scality~utapi~Y5MREV.dockerbuild Expired
33 KB
sha256:8cc64c71bd95b63d50e03841324d709ae143ab9c392e60bf698303f18ebd7fe7