Skip to content

change computation of typebounds #4785

change computation of typebounds

change computation of typebounds #4785

Triggered via push November 28, 2024 14:09
Status Success
Total duration 20m 36s
Artifacts 3

test.yml

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

Annotations

6 warnings
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/
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/
build-test-deploy-container: .github/workflows/test.yml#L1
Java used up to 4.81096GB of RAM
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/
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/

Artifacts

Produced during runtime
Name Size
pidstat.txt
42.6 KB
viperproject~gobra~Q1TA2P.dockerbuild
46.2 KB
viperproject~gobra~TEU1SJ.dockerbuild
69.5 KB