Skip to content

Make a Merge() call allow not-yet-recognized new fields in P4Info files #103

Make a Merge() call allow not-yet-recognized new fields in P4Info files

Make a Merge() call allow not-yet-recognized new fields in P4Info files #103

Triggered via pull request September 1, 2024 00:03
Status Failure
Total duration 1m 42s
Artifacts 2

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
test
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: Dockerfile.dev#L8
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: Dockerfile#L5
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: Dockerfile#L27
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: Dockerfile#L28
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: Dockerfile#L4
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
p4lang~p4runtime-shell~HZ0B88.dockerbuild
52.9 KB
p4lang~p4runtime-shell~PEWB52.dockerbuild
32.4 KB