bump arsenal #748
tests.yaml
on: push
build-ci
/
...
/
build
20s
lint
19s
Annotations
12 errors and 28 warnings
lint
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 unit tests
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 v2 soft limit test
Process completed with exit code 1.
|
run v1 server tests
Process completed with exit code 1.
|
tests-v2-with-vault
The job running on runner ubuntu-22.04-2core_1c751684e9c5 has exceeded the maximum execution time of 360 minutes.
|
tests-v2-with-vault
An error occurred when attempting to determine the step timeout.
|
tests-v2-with-vault
The template is not valid. .github/workflows/tests.yaml (Line: 237, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,.github/workflows/tests.yaml (Line: 237, Col: 24): Unexpected value ''
|
tests-v2-with-vault
Process completed with exit code 1.
|
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
|
lint
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
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#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/
|
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/
|
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#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#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#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/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:
.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 v1 cron tests
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run v1 interval tests
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run unit tests
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run v1 client tests
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run v2 hard limit test
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run v2 soft limit test
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
run v1 server tests
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
tests-v2-with-vault
Cache not found for keys: node-cache-Linux-x64-yarn-20d38a05cf1b4814ee7fa8fda5ef64308c44e4ea11698fb3d9260c86deeb31da
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
scality~utapi~KF00VH.dockerbuild
|
28 KB |
|
scality~utapi~LGA1T2.dockerbuild
|
34.7 KB |
|
scality~utapi~MEP04H.dockerbuild
|
49 KB |
|