Use option --respectFunctionPrePermAmounts
in the backends
#4812
test.yml
on: pull_request
build-test-deploy-container
19m 45s
Annotations
8 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 4.97424GB of RAM
|
build-test-deploy-container:
.github/workflows/test.yml#L1
Z3 used up to 0.501656GB 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
|
41.5 KB |
|
viperproject~gobra~DHKYY7.dockerbuild
|
67.4 KB |
|
viperproject~gobra~P9BG9J.dockerbuild
|
45.4 KB |
|