Skip to content
test

fix #4770

Sign in to view logs

fix

fix #4770

Triggered via push November 16, 2024 09:10
@jcp19jcp19
pushed 3f832e2
fix-bounds-singed-ints
Status Success
Total duration 21m 8s
Artifacts 3

test.yml

on: push
build-test-deploy-container
20m 58s
build-test-deploy-container
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
The 'as' keyword should match the case of the 'from' keyword: workflow-container/Dockerfile#L7
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: workflow-container/Dockerfile#L35
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-test-deploy-container: .github/workflows/test.yml#L1
Java used up to 4.99233GB of RAM
Legacy key/value format with whitespace separator should not be used: workflow-container/Dockerfile#L75
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/
The 'as' keyword should match the case of the 'from' keyword: workflow-container/Dockerfile#L7
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: workflow-container/Dockerfile#L35
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/

Artifacts

Produced during runtime
Name Size
pidstat.txt
42.2 KB
viperproject~gobra~3WS27S.dockerbuild
70.4 KB
viperproject~gobra~TAPE8I.dockerbuild
45.9 KB