Skip to content

fixup

fixup #725

Triggered via push January 8, 2025 15:56
Status Cancelled
Total duration 28m 33s
Artifacts 3

tests.yaml

on: push
build-ci  /  ...  /  build
24s
build-ci / warp10-ci / build
build-ci  /  vault-ci
13s
build-ci / vault-ci
build-ci  /  ...  /  build
43s
build-ci / redis-ci / build
build-ci  /  ...  /  build
18s
build-ci / redis-replica-ci / build
tests-v2-with-vault
7m 2s
tests-v2-with-vault
Matrix: tests-v1
Matrix: tests-v2-without-sensision
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 33 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: 230, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,.github/workflows/tests.yaml (Line: 230, Col: 24): Unexpected value ''
run v2 hard limit test
The run was canceled by @benzekrimaha.
run v2 hard limit test
An error occurred when attempting to determine the step timeout.
run v2 hard limit test
The template is not valid. .github/workflows/tests.yaml (Line: 353, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,.github/workflows/tests.yaml (Line: 353, Col: 24): Unexpected value ''
run v2 soft limit test
The run was canceled by @benzekrimaha.
run v2 soft limit test
An error occurred when attempting to determine the step timeout.
run v2 soft limit test
The template is not valid. .github/workflows/tests.yaml (Line: 353, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,.github/workflows/tests.yaml (Line: 353, Col: 24): Unexpected value ''
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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
build-ci / warp10-ci / build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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#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/
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#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#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#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/
build-ci / redis-ci / build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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 / redis-replica-ci / build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
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/
run unit tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run v1 server tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run v1 client tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run v1 cron tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run v1 interval tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run v2 hard limit test
Docker pull failed with exit code 1, back off 8.235 seconds before retry.

Artifacts

Produced during runtime
Name Size
scality~utapi~IFEDET.dockerbuild
48.7 KB
scality~utapi~L19656.dockerbuild
28.3 KB
scality~utapi~QUTYZ0.dockerbuild
36 KB