Skip to content

Change the default interpretation of access predicates in function preconditions according to the new semantics of Viper #5039

Change the default interpretation of access predicates in function preconditions according to the new semantics of Viper

Change the default interpretation of access predicates in function preconditions according to the new semantics of Viper #5039

Triggered via pull request February 7, 2025 14:41
Status Failure
Total duration 44m 53s
Artifacts 2

test.yml

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

Annotations

2 errors and 2 warnings
build-test-deploy-container: .github/workflows/test.yml#L1
Z3 used up to 13.5295GB of RAM
build-test-deploy-container
Process completed with exit code 1.
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/

Artifacts

Produced during runtime
Name Size
pidstat.txt
105 KB
viperproject~gobra~PS50I4.dockerbuild
67.5 KB