go icon indicating copy to clipboard operation
go copied to clipboard

x/build: I/O error on netbsd-arm-bsiegert builder

Open gopherbot opened this issue 2 years ago • 1 comments

#!watchflakes
post <- builder == "netbsd-arm-bsiegert" && `creating work dir:.*input/output error`

Issue created automatically to collect these failures.

Example (log):

go: creating work dir: mkdir /var/gobuilder/buildlet/tmp/go-build894810787: input/output error

go tool dist: FAILED: go list -f={{if .Stale}}	STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std: exit status 1

watchflakes

gopherbot avatar Dec 20 '22 23:12 gopherbot

Found new dashboard test flakes for:

#!watchflakes
post <- section == "Testing packages." && test == ""
2022-12-08 15:23 netbsd-arm-bsiegert go@0aad4d32 (log)
go: creating work dir: mkdir /var/gobuilder/buildlet/tmp/go-build894810787: input/output error

go tool dist: FAILED: go list -f={{if .Stale}}	STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std: exit status 1

watchflakes

gopherbot avatar Dec 20 '22 23:12 gopherbot

(attn @bsiegert)

bcmills avatar Nov 27 '23 15:11 bcmills

Found new dashboard test flakes for:

#!watchflakes
default <- builder == "netbsd-arm-bsiegert" && `input/output error`
2023-11-21 20:23 netbsd-arm-bsiegert vuln@286bb05c go@5f7a4085 x/vuln/internal/buildinfo.Test58509 (log)
--- FAIL: Test58509 (123.57s)
    --- FAIL: Test58509/var (119.87s)
        additions_scan_test.go:149: failed to build the binary exit status 1 # golang.org/entry
            /var/gobuilder/buildlet/go/pkg/tool/netbsd_arm/link: resize output file failed: truncate $WORK/b001/exe/a.out: input/output error
2023-11-21 20:23 netbsd-arm-bsiegert vuln@286bb05c go@5f7a4085 x/vuln/internal/buildinfo.TestStrippedBinary (log)
--- FAIL: TestStrippedBinary (5.44s)
    --- FAIL: TestStrippedBinary/linux/amd64 (0.39s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest1579259207: input/output error
    --- FAIL: TestStrippedBinary/linux/386 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest2104941465: input/output error
    --- FAIL: TestStrippedBinary/linux/arm (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest344040616: input/output error
    --- FAIL: TestStrippedBinary/linux/arm64 (0.39s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest2273657939: input/output error
    --- FAIL: TestStrippedBinary/windows/amd64 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest2210959540: input/output error
    --- FAIL: TestStrippedBinary/windows/386 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest2750132037: input/output error
    --- FAIL: TestStrippedBinary/windows/arm (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest3050967889: input/output error
    --- FAIL: TestStrippedBinary/windows/arm64 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest1133147062: input/output error
    --- FAIL: TestStrippedBinary/freebsd/amd64 (0.47s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest186036776: input/output error
    --- FAIL: TestStrippedBinary/freebsd/386 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest424473412: input/output error
    --- FAIL: TestStrippedBinary/freebsd/arm (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest2520640105: input/output error
    --- FAIL: TestStrippedBinary/freebsd/arm64 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest1832074828: input/output error
    --- FAIL: TestStrippedBinary/darwin/amd64 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest3262043378: input/output error
    --- FAIL: TestStrippedBinary/darwin/arm64 (0.38s)
        buildtest.go:49: mkdir /var/gobuilder/buildlet/tmp/buildtest3106340921: input/output error

watchflakes

gopherbot avatar Nov 27 '23 15:11 gopherbot

This is an unfortunate failure mode of this builder. Every once in a while, it loses track of its USB storage (???), at which point in-progress builds fail with "i/o error" before the machine eventually stops responding completely.

For now, I rebooted the builder. I assume that this will improve with the move to LUCI, since the swarming bot reboots the machine from time to time.

bsiegert avatar Nov 28 '23 10:11 bsiegert