Reinstate the usage of the SilFrontend API and support for the refute statement #4846
jcp19test.yml
on: pull_request
build-test-deploy-container
21m 25s
Annotations
7 warnings
|
build-test-deploy-container
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
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 5.01012GB 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
|
44.2 KB |
|
|
viperproject~gobra~E72CGO.dockerbuild
|
68.8 KB |
|
|
viperproject~gobra~EQJSZK.dockerbuild
|
46.4 KB |
|