bump #734
williamlardiertests.yaml
on: push
build-ci
/
...
/
build
19s
lint
2m 2s
Annotations
1 error and 54 warnings
|
run v1 cron tests
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/
|
|
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/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#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/
|
|
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#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#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#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#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#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/
|
|
lint
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
lint:
libV2/server/API/metrics/listMetrics.js#L26
'start' is never reassigned. Use 'const' instead
|
|
lint:
tests/functional/client/testClientConnections.js#L60
Expected to return a value at the end of arrow function
|
|
lint:
tests/functional/client/testClientConnections.js#L109
Expected to return a value at the end of arrow function
|
|
lint:
tests/functional/v2/task/testReindex.js#L191
Unexpected block statement surrounding arrow body; parenthesize the returned value and move it immediately after the `=>`
|
|
lint:
tests/utils/vaultclient.js#L132
Expected to return a value at the end of arrow function
|
|
run unit tests
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip
|
|
run unit tests
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
run unit 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 cron tests
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip
|
|
run v1 cron tests
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
run v1 server 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 server tests
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip
|
|
run v1 server tests
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
run v1 server 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: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
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-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.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 interval tests
Cache not found for keys: setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip
|
|
run v1 interval 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 interval 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 interval tests
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
run v2 soft limit test
Cache not found for keys: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
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
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-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.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-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.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: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
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: node-cache-Linux-x64-yarn-38226ef32d4efbb11ca737cd3373c2b34d8b004f99dd20194a942168ed6b1d26
|
|
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-24.04-Ubuntu-python-3.9.21-pip-66de078fa5ea011a344b15ec417682f49dc563a392c0e57167178f41b2f063c2, setup-python-Linux-x64-24.04-Ubuntu-python-3.9.21-pip
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
scality~utapi~D5VU37.dockerbuild
|
35 KB |
|
|
scality~utapi~K87FBZ.dockerbuild
|
28.5 KB |
|
|
scality~utapi~P6QQC4.dockerbuild
|
49.8 KB |
|