Skip to content
test-os

test-os #365

Sign in to view logs

test-os

test-os #365

Triggered via schedule October 9, 2024 10:01
@jsternbergjsternberg
⁠ e8c0115
master
Status Failure
Total duration 11m 36s
Artifacts 11

test-os.yml

on: schedule
Matrix: build
test-freebsd-amd64
3m 10s
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#L52
InvalidDefinitionDescription: Comment for FROM should follow the format: `# runc-src <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#L446
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#L143
InvalidDefinitionDescription: Comment for FROM should follow the format: `# dnsname-src <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#L252
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#L200
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#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#L40
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#L79
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#L101
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#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#L87
InvalidDefinitionDescription: Comment for FROM should follow the format: `# buildctl <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#L252
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#L446
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#L59
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#L101
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#L200
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#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#L52
InvalidDefinitionDescription: Comment for FROM should follow the format: `# runc-src <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#L143
InvalidDefinitionDescription: Comment for FROM should follow the format: `# dnsname-src <description>` More info: https://docs.docker.com/go/dockerfile/rule/invalid-definition-description/
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, ./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, ./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, ./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, ./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 (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
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

Artifacts

Produced during runtime
Name Size
buildkit-freebsd-amd64 Expired
69.6 MB
buildkit-windows-amd64 Expired
78.1 MB
jsternberg~buildkit~50RDUR.dockerbuild Expired
64.9 KB
jsternberg~buildkit~TBW3SX.dockerbuild Expired
66.5 KB
test-reports-test-windows-amd64--1- Expired
2.93 MB
test-reports-test-windows-amd64-client--containerd Expired
5.27 KB
test-reports-test-windows-amd64-cmdbuildctl--containerd Expired
4.02 KB
test-reports-test-windows-amd64-frontend--containerd Expired
1.27 KB
test-reports-test-windows-amd64-frontenddockerfile--containerd Expired
2.08 KB
test-reports-test-windows-amd64-solver--containerd Expired
17.7 KB
test-reports-test-windows-amd64-workercontainerd--containerd Expired
1.42 KB