Skip to content

pick arsenal exisiting sha #751

pick arsenal exisiting sha

pick arsenal exisiting sha #751

Triggered via push March 12, 2025 21:19
Status Failure
Total duration 7m 0s
Artifacts 3

tests.yaml

on: push
build-ci  /  ...  /  build
1m 51s
build-ci / warp10-ci / build
build-ci  /  vault-ci
45s
build-ci / vault-ci
build-ci  /  ...  /  build
27s
build-ci / redis-ci / build
build-ci  /  ...  /  build
19s
build-ci / redis-replica-ci / build
tests-v2-with-vault
3m 42s
tests-v2-with-vault
Matrix: tests-v1
Matrix: tests-v2-without-sensision
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 32 warnings
run v1 server tests
Process completed with exit code 7.
run v1 cron tests
Process completed with exit code 2.
run v1 interval tests
Process completed with exit code 2.
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/
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: .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/
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#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/
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/
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#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#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#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#L32
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#L33
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/
lint
Cache not found for keys: node-cache-Linux-x64-yarn-906c5113a595949e770d2e593c820119a8bcef24dd7fe3e2f394ac865bf21b3e
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 v2 hard limit test
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
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 soft limit test
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
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 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 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 client tests
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
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 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
tests-v2-with-vault
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
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~D7BWLE.dockerbuild Expired
76.8 KB
sha256:d6dd33fd4b1d0f340f63559581512ce31f80fe7498722b3b25f4de4a4c259e0f
scality~utapi~I6Z6V5.dockerbuild Expired
43.4 KB
sha256:0c14d35fd19aaf985c388ac1c8830db10fdc9693b1041441436cad2ecd8928b0
scality~utapi~K9V7MJ.dockerbuild Expired
28.8 KB
sha256:92a5e7f9e43dea65cdbd7f8fcaf13f38b259f89f309a65bdcdfe25f403043999