Skip to content

Revert "Add refute statement" #4737

Revert "Add refute statement"

Revert "Add refute statement" #4737

Re-run triggered September 26, 2024 13:08
Status Success
Total duration 16m 9s
Artifacts 3

test.yml

on: pull_request
build-test-deploy-container
15m 55s
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.9104GB 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
43.4 KB
viperproject~gobra~EPDNK0.dockerbuild
39.7 KB
viperproject~gobra~ND199Q.dockerbuild
56.1 KB