Skip to content

arsenal bump

arsenal bump #758

Re-run triggered March 17, 2025 15:30
Status Failure
Total duration 5m 17s
Artifacts 3

tests.yaml

on: push
build-ci  /  ...  /  build
20s
build-ci / warp10-ci / build
build-ci  /  vault-ci
11s
build-ci / vault-ci
build-ci  /  ...  /  build
26s
build-ci / redis-ci / build
build-ci  /  ...  /  build
20s
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

8 errors and 28 warnings
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 v1 interval tests
Process completed with exit code 1.
run v1 server tests
Process completed with exit code 1.
run v2 hard limit test
Process completed with exit code 1.
tests-v2-with-vault
Process completed with exit code 1.
run v2 soft limit test
Process completed with exit code 1.
lint
Cache not found for keys: node-cache-Linux-x64-yarn-61757c324a65f412f338aecdd889b4aa56d4b67b94f3a7416c212c40075cd016
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#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/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/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#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/
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/
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/
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#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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: images/warp10/Dockerfile#L57
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#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: .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/
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 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 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 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 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
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
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