Skip to content
test-os

test-os #76

Sign in to view logs

test-os

test-os #76

Triggered via schedule October 10, 2024 10:00
@mendsleymendsley
⁠ d4e6655
pew/main
Status Failure
Total duration 14m 17s
Artifacts 11

test-os.yml

on: schedule
Matrix: build
test-freebsd-amd64
2m 56s
test-freebsd-amd64
Matrix: test-windows-amd64
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 29 warnings
test-freebsd-amd64
Process completed with exit code 1.
test-freebsd-amd64
Process completed with exit code 1.
test-freebsd-amd64
Process completed with exit code 1.
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L6
InvalidDefinitionDescription: Comment for ARG should follow the format: `# CONTAINERD_ALT_VERSION_16 <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L69
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildkit-version <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L97
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildkitd <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L190
InvalidDefinitionDescription: Comment for ARG should follow the format: `# BUILDKIT_SBOM_SCAN_STAGE <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L234
InvalidDefinitionDescription: Comment for FROM should follow the format: `# containerd-alt-16 <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L422
InvalidDefinitionDescription: Comment for FROM should follow the format: `# rootless <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L33
InvalidDefinitionDescription: Comment for FROM should follow the format: `# golatest <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L36
InvalidDefinitionDescription: Comment for FROM should follow the format: `# gobuild-base <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L41
InvalidDefinitionDescription: Comment for FROM should follow the format: `# dlv <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L48
InvalidDefinitionDescription: Comment for FROM should follow the format: `# runc <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L41
InvalidDefinitionDescription: Comment for FROM should follow the format: `# dlv <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L234
InvalidDefinitionDescription: Comment for FROM should follow the format: `# containerd-alt-16 <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L97
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildkitd <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L139
InvalidDefinitionDescription: Comment for FROM should follow the format: `# dnsname <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L6
InvalidDefinitionDescription: Comment for ARG should follow the format: `# CONTAINERD_ALT_VERSION_16 <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L33
InvalidDefinitionDescription: Comment for FROM should follow the format: `# golatest <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L36
InvalidDefinitionDescription: Comment for FROM should follow the format: `# gobuild-base <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L48
InvalidDefinitionDescription: Comment for FROM should follow the format: `# runc <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L69
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildkit-version <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
Comment for build stage or argument should follow the format: `# <arg/stage name> <description>`. If this is not intended to be a description comment, add an empty line or comment between the instruction and the comment.: Dockerfile#L83
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildctl <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
test-windows-amd64 (containerd, ./cmd/buildctl)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-freebsd-amd64
macOS's Gatekeeper has been disabled for this Cask
test-freebsd-amd64
macOS's Gatekeeper has been disabled for this Cask
test-windows-amd64 (containerd, ./frontend)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-windows-amd64 (containerd, ./solver)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-windows-amd64 (containerd, ./worker/containerd)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-windows-amd64 (containerd, ./client)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-windows-amd64 (./..., 1)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1
test-windows-amd64 (containerd, ./frontend/dockerfile)
Codecov: Failed to properly create commit: The process 'D:\a\_actions\codecov\codecov-action\v4\dist\codecov.exe' failed with exit code 1

Artifacts

Produced during runtime
Name Size
PlayEveryWare~buildkit~7WQ8BK.dockerbuild Expired
64.5 KB
PlayEveryWare~buildkit~ZD7JAX.dockerbuild Expired
64.7 KB
buildkit-freebsd-amd64 Expired
69.7 MB
buildkit-windows-amd64 Expired
78.3 MB
test-reports-test-windows-amd64--1- Expired
2.92 MB
test-reports-test-windows-amd64-client--containerd Expired
22.9 KB
test-reports-test-windows-amd64-cmdbuildctl--containerd Expired
3.62 KB
test-reports-test-windows-amd64-frontend--containerd Expired
1.14 KB
test-reports-test-windows-amd64-frontenddockerfile--containerd Expired
34.9 KB
test-reports-test-windows-amd64-solver--containerd Expired
11.9 KB
test-reports-test-windows-amd64-workercontainerd--containerd Expired
1.41 KB