Skip to content

Fix issue #781

Fix issue #781 #4726

Triggered via pull request August 27, 2024 06:40
Status Success
Total duration 23m 37s
Artifacts 3

test.yml

on: pull_request
build-test-deploy-container
23m 27s
build-test-deploy-container
Fit to window
Zoom out
Zoom in

Annotations

7 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.98767GB of RAM
build-test-deploy-container: .github/workflows/test.yml#L1
Z3 used up to 0.625136GB 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 Expired
46.5 KB
viperproject~gobra~4M5AX4.dockerbuild Expired
95 KB
viperproject~gobra~V83N8K.dockerbuild Expired
46.4 KB