Skip to content

Better retry configuration for jobs #22663

Better retry configuration for jobs

Better retry configuration for jobs #22663

Triggered via pull request November 21, 2025 00:20
Status Success
Total duration 4m 1s
Artifacts 5

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L50
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L6
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: Dockerfile#L60
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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L38
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_ACCESS_KEY_ID") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L96
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: Dockerfile#L62
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: Dockerfile#L61
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: Dockerfile#L36
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: Dockerfile#L38
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/
coverage-report
main is missing merged-coverage.xml. See documentation on how to add this
coverage-report
No artifacts found for the following workspaces: ci,cron

Artifacts

Produced during runtime
Name Size Digest
minitest-coverage Expired
48.6 KB
sha256:35be49a9d16fb75d38809b448f78f024427cee6cdcfe3cde5a6abf8d62fa4593
minitest-reports Expired
26 KB
sha256:2263536f75039517cf9a82859c754970bc06c558b0aed826264679aa7febfd62
neinteractiveliterature~intercode~NU9U76.dockerbuild Expired
126 KB
sha256:52dfc8b5cdc77c2b0ba6cd24dd9dfe01fd8054d1cf8b76a9a17c07194ab13c30
vitest-coverage Expired
88.6 KB
sha256:03c1122f58d98ebbadcb6f86eca82beca3ebbc0746ad0c93162987c073ba1b04
vitest-reports Expired
537 KB
sha256:f0e34b12a85f7e9d1325789d3704fa7cc1dde04209119fc1bd3d90530dbc6a3f