fixup #744
benzekrimaha
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
tests.yaml
on: push
build-ci
/
...
/
build
21s
lint
2m 28s
Annotations
2 errors and 38 warnings
|
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 ''
|
|
lint
Cache not found for keys: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
lint:
lib/server.js#L140
Strings must use singlequote
|
|
lint:
libV2/server/index.js#L65
Strings must use singlequote
|
|
lint:
tests/utils/mock/BucketD.js#L199
Strings must use singlequote
|
|
lint:
tests/utils/mock/Vault.js#L24
Strings must use singlequote
|
|
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
|
|
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#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#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/
|
|
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#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#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/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/
|
|
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:
.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/
|
|
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-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
run v2 hard limit test
Cache not found for keys: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
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 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: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
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 unit tests
Cache not found for keys: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
run v1 cron 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: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
run v2 soft limit test
Cache not found for keys: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
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 v1 client tests
Cache not found for keys: node-cache-Linux-x64-yarn-8991e3f46c8a1418ea56424b91a37120f2747b52bec63c3b35329ce0bf2eded1
|
|
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
|