test-os #639
sipsmatest-os.yml
on: schedule
Matrix: build
test-freebsd-amd64
3m 39s
Matrix: test-windows-amd64
Annotations
7 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.
|
|
Failed: frontend/dockerfile/TestIntegration:
frontend/dockerfile/run.go#L272
=== RUN TestIntegration
run.go:272: copied docker.io/wintools/nanoserver:ltsc2022 to local mirror localhost:65000/library/nanoserver:plus-busybox
time="2024-10-09T10:05:53Z" level=info msg="trying next host - response was http.StatusNotFound" host="localhost:65000"
run.go:272: copied mcr.microsoft.com/windows/nanoserver:ltsc2022 to local mirror localhost:65000/library/nanoserver:latest
time="2024-10-09T10:05:55Z" level=info msg="trying next host - response was http.StatusNotFound" host="localhost:65000"
run.go:272: copied docker.io/wintools/nanoserver:ltsc2022 to local mirror localhost:65000/library/nanoserver:plus
run.go:272: copied mcr.microsoft.com/windows/nanoserver:ltsc2022 to local mirror localhost:49181/library/nanoserver:latest
time="2024-10-09T10:22:51Z" level=info msg="trying next host - response was http.StatusNotFound" host="localhost:49181"
run.go:272: copied docker.io/wintools/nanoserver:ltsc2022 to local mirror localhost:49181/library/nanoserver:plus
time="2024-10-09T10:22:53Z" level=info msg="trying next host - response was http.StatusNotFound" host="localhost:49181"
run.go:272: copied docker.io/wintools/nanoserver:ltsc2022 to local mirror localhost:49181/library/nanoserver:plus-busybox
run.go:213:
Error Trace: D:/a/buildkit/buildkit/util/testutil/integration/run.go:213
D:/a/buildkit/buildkit/util/testutil/integration/run.go:214
D:/a/buildkit/buildkit/frontend/dockerfile/dockerfile_test.go:264
Error: Should be true
Test: TestIntegration
--- FAIL: TestIntegration (1183.40s)
|
|
Failed: frontend/dockerfile/TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin:
frontend/dockerfile/sandbox.go#L135
=== RUN TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin
sandbox.go:135: stderr: D:\a\buildkit\buildkit\bin\containerd.exe --config C:\Users\RUNNER~1\AppData\Local\Temp\bktest_containerd3451783915\config.toml
sandbox.go:138: > StartCmd 2024-10-09 10:25:33.734771 +0000 UTC m=+1182.747204901 D:\a\buildkit\buildkit\bin\containerd.exe --config C:\Users\RUNNER~1\AppData\Local\Temp\bktest_containerd3451783915\config.toml
sandbox.go:138: time="2024-10-09T10:25:33Z" level=warning msg="containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup"
sandbox.go:138: time="2024-10-09T10:25:33.786655200Z" level=info msg="starting containerd" revision=472731909fa34bd7bc9c087e4c27943f9835f111 version=v1.7.21
sandbox.go:138: time="2024-10-09T10:25:33.786655200Z" level=debug msg="Stackdump - waiting signal at Global\\stackdump-1756"
sandbox.go:138: time="2024-10-09T10:25:33.802327700Z" level=info msg="loading plugin \"io.containerd.event.v1.exchange\"..." type=io.containerd.event.v1
sandbox.go:138: time="2024-10-09T10:25:33.802854900Z" level=info msg="loading plugin \"io.containerd.internal.v1.opt\"..." type=io.containerd.internal.v1
sandbox.go:138: time="2024-10-09T10:25:33.802908700Z" level=info msg="loading plugin \"io.containerd.warning.v1.deprecations\"..." type=io.containerd.warning.v1
sandbox.go:138: time="2024-10-09T10:25:33.802908700Z" level=info msg="loading plugin \"io.containerd.snapshotter.v1.windows-lcow\"..." type=io.containerd.snapshotter.v1
sandbox.go:138: time="2024-10-09T10:25:33.803744600Z" level=info msg="loading plugin \"io.containerd.snapshotter.v1.windows\"..." type=io.containerd.snapshotter.v1
sandbox.go:138: time="2024-10-09T10:25:33.803794300Z" level=info msg="loading plugin \"io.containerd.content.v1.content\"..." type=io.containerd.content.v1
sandbox.go:138: time="2024-10-09T10:25:33.804610100Z" level=info msg="loading plugin \"io.containerd.metadata.v1.bolt\"..." type=io.containerd.metadata.v1
sandbox.go:138: time="2024-10-09T10:25:33.805207800Z" level=info msg="metadata content store policy set" policy=shared
sandbox.go:138: time="2024-10-09T10:25:33.816473500Z" level=info msg="loading plugin \"io.containerd.gc.v1.scheduler\"..." type=io.containerd.gc.v1
sandbox.go:138: time="2024-10-09T10:25:33.816473500Z" level=info msg="loading plugin \"io.containerd.differ.v1.windows-lcow\"..." type=io.containerd.differ.v1
sandbox.go:138: time="2024-10-09T10:25:33.818091300Z" level=info msg="loading plugin \"io.containerd.differ.v1.walking\"..." type=io.containerd.differ.v1
sandbox.go:138: time="2024-10-09T10:25:33.818091300Z" level=info msg="loading plugin \"io.containerd.differ.v1.windows\"..." type=io.containerd.differ.v1
sandbox.go:138: time="2024-10-09T10:25:33.818091300Z" level=info msg="loading plugin \"io.containerd.lease.v1.manager\"..." type=io.containerd.lease.v1
sandbox.go:138: time="2024-10-09T10:25:33.818298800Z" level=info msg="loading plugin \"io.containerd.streaming.v1.manager\"..." type=io.containerd.streaming.v1
sandbox.go:138: time="2024-10-09T10:25:33.818367600Z" level=info msg="loading plugin \"io.containerd.runtime.v2.task\"..." type=io.containerd.runtime.v2
sandbox.go:138: time="2024-10-09T10:25:33.818532100Z" level=info msg="loading plugin \"io.containerd.runtime.v2.shim\"..." type=io.containerd.runtime.v2
sandbox.go:138: time="2024-10-09T10:25:33.818532100Z" level=info msg="loading plugin \"io.containerd.sandbox.store.v1.local\"..." type=io.containerd.sandbox.store.v1
sandbox.go:138: time="2024-10-09T10:25:33.818532100Z" level=info msg="loading plugin \"io.containerd.sandbox.controller.v1.local\"..." type=io.containerd.sandbox.controller.v1
sandbox.go:138: time="2024-10-09T10:25:33.819216900Z" level=info msg="loading plugin \"io.containerd.service.v1.containers-service\"..." type=io.containerd.service.v1
sandbox.go:138: time="2
|
|
Failed: frontend/dockerfile/TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin/warntype=progress:
frontend/dockerfile/dockerfile_lint_test.go#L1514
=== RUN TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin/warntype=progress
dockerfile_lint_test.go:1514:
Error Trace: D:/a/buildkit/buildkit/frontend/dockerfile/dockerfile_lint_test.go:1525
D:/a/buildkit/buildkit/frontend/dockerfile/dockerfile_lint_test.go:1483
D:/a/buildkit/buildkit/frontend/dockerfile/dockerfile_lint_test.go:1514
Error: Not equal:
expected: "SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG \"super_duper_secret_token\") (line 6)"
actual : "SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG \"auth\") (line 6)"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "super_duper_secret_token") (line 6)
+SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "auth") (line 6)
Test: TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin/warntype=progress
--- FAIL: TestIntegration/TestSecretsUsedInArgOrEnv/worker=containerd/frontend=builtin/warntype=progress (0.22s)
|
|
test-windows-amd64 (containerd, ./frontend/dockerfile)
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#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#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#L83
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#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#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#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#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#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#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/
|
|
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#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#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#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/
|
|
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, ./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-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-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 (./..., 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 | |
|---|---|---|
|
buildkit-freebsd-amd64
Expired
|
69.7 MB |
|
|
buildkit-windows-amd64
Expired
|
78.3 MB |
|
|
sipsma~buildkit~4UFVJW.dockerbuild
|
63.9 KB |
|
|
sipsma~buildkit~VLYMK0.dockerbuild
|
63.3 KB |
|
|
test-reports-test-windows-amd64--1-
Expired
|
2.92 MB |
|
|
test-reports-test-windows-amd64-client--containerd
Expired
|
23.2 KB |
|
|
test-reports-test-windows-amd64-cmdbuildctl--containerd
Expired
|
3.63 KB |
|
|
test-reports-test-windows-amd64-frontend--containerd
Expired
|
1.13 KB |
|
|
test-reports-test-windows-amd64-frontenddockerfile--containerd
Expired
|
44.5 KB |
|
|
test-reports-test-windows-amd64-solver--containerd
Expired
|
11.9 KB |
|
|
test-reports-test-windows-amd64-workercontainerd--containerd
Expired
|
1.41 KB |
|