bump latest arsenal #753
tests.yaml
on: push
build-ci
/
...
/
build
16s
lint
2m 30s
Annotations
9 errors and 36 warnings
|
lint
Process completed with exit code 1.
|
|
run v2 soft limit test
Process completed with exit code 1.
|
|
run v1 client tests
Process completed with exit code 1.
|
|
run v2 hard limit test
Process completed with exit code 1.
|
|
run unit tests
Process completed with exit code 1.
|
|
run v1 interval tests
Process completed with exit code 1.
|
|
run v1 server tests
Process completed with exit code 1.
|
|
run v1 cron 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/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:
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#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#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#L34
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#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#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#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/
|
|
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/
|
|
lint
Cache not found for keys: node-cache-Linux-x64-yarn-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
run v2 soft limit test
Cache not found for keys: node-cache-Linux-x64-yarn-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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 client tests
Cache not found for keys: node-cache-Linux-x64-yarn-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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 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-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
tests-v2-with-vault
Cache not found for keys: node-cache-Linux-x64-yarn-4cde9ff23b6fb97ac7f96361cad11f7ce28157003b233472f33e252f10f81a85
|
|
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~00QOTY.dockerbuild
Expired
|
46.2 KB |
sha256:ff2cce287e903a97a1abb56eefad58067bc2acf9fde99bf516d2b4e3d58bc039
|
|
|
scality~utapi~R3C5MF.dockerbuild
Expired
|
33 KB |
sha256:f1f01c166d15fe9f0efaa5068d15332a502a3d2ee9ce976fe054a21d84ed2bb9
|
|
|
scality~utapi~X30B3V.dockerbuild
Expired
|
27.9 KB |
sha256:342a4cc01ef555c1a6ddfd8927bd7650710d7e9ca24a055dee90202acd138880
|
|