Skip to content

JLAI-CI

JLAI-CI #23

Manually triggered August 28, 2024 13:01
Status Cancelled
Total duration 50s
Artifacts 2

jlai.yml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
jlai-p3
buildx failed with: ERROR: failed to solve: process "/bin/sh -c julia -e 'import Pkg; Pkg.activate(\".\"); Pkg.instantiate(); Pkg.precompile()'" did not complete successfully: exit code: 1
jlai-p2
The run was canceled by @a-mhamdi.
jlai-p2
The operation was canceled.
Legacy key/value format with whitespace separator should not be used: Docker/Dockerfile-1#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: Docker/Dockerfile-1#L9
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: Docker/Dockerfile-1#L10
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: Docker/Dockerfile-1#L11
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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Docker/Dockerfile-1#L38
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Artifacts

Produced during runtime
Name Size
a-mhamdi~jlai~KQL5DG.dockerbuild Expired
9.07 KB
a-mhamdi~jlai~WG3HBC.dockerbuild Expired
11.9 KB