go: x/benchmarks/sweet/cmd/sweet: TestSweetEndToEnd failing with gvisor build errors since CL 386698

TestSweetEndToEnd is persistently failing on the linux-amd64-longtest and linux-amd64-perf builders since CL 386698 (attn @dr2chase, @prattmic, @aclements).

--- FAIL: TestSweetEndToEnd (181.32s)
    integration_test.go:128: no results produced.
    integration_test.go:150: command output:
        [sweet] Work directory: /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5
        [sweet] Benchmarks: gvisor
        [sweet] Setting up benchmark: gvisor
        [shell] git clone -b go https://github.com/google/gvisor /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/src
        [shell] git -C /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/src checkout 6392b0f3bea052af0de9d95677233dd9e442dbd5
        [shell] mkdir -p /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/results-5/gvisor
        [shell] mkdir -p /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/go/bin
        [shell] mkdir -p /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/src
        [shell] mkdir -p /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/go/tmp
        [shell] mkdir -p /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/go/assets
        [shell] cd /workdir/gopath/src/golang.org/x/benchmarks/sweet/benchmarks/gvisor
        [shell] /workdir/go/bin/go build -o /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/go/bin/gvisor-bench
        [shell] cd /workdir/gopath/src/golang.org/x/benchmarks/sweet/cmd/sweet
        [shell] cd /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/src/runsc
        [shell] CGO_ENABLED=0 /workdir/go/bin/go build -o /workdir/gopath/src/golang.org/x/benchmarks/sweet/tmp/tmp-5/gvisor/go/bin/runsc
        [shell] cd /workdir/gopath/src/golang.org/x/benchmarks/sweet/cmd/sweet
        [sweet] error: build gvisor for go: exit status 1
        [sweet] error: failed to execute benchmarks, see log for details
    integration_test.go:151: exit status 1
FAIL
FAIL	golang.org/x/benchmarks/sweet/cmd/sweet	181.334s

greplogs --dashboard -md -l -e 'error: build gvisor for .*: exit status 1'

2022-03-02T20:53:54-55644cf-bcb89fc/linux-amd64-longtest 2022-03-02T20:14:06-55644cf-2cb9e11/linux-amd64-longtest 2022-03-02T20:02:12-55644cf-fc5b64e/linux-amd64-longtest 2022-03-02T18:21:38-55644cf-986b04c/linux-amd64-longtest 2022-03-02T18:06:42-55644cf-a5b8b56/linux-amd64-longtest 2022-03-02T17:47:07-55644cf-6c6a8fb/linux-amd64-longtest 2022-03-02T17:42:53-55644cf-5a03cbd/linux-amd64-longtest 2022-03-02T17:03:04-55644cf-4a13f6f/linux-amd64-longtest 2022-03-02T16:54:21-55644cf-f79a983/linux-amd64-longtest 2022-03-02T11:49:04-55644cf-40e24a9/linux-amd64-longtest 2022-03-02T11:49:04-55644cf-40e24a9/linux-amd64-perf 2022-03-02T11:33:18-55644cf-fd2e1e7/linux-amd64-longtest 2022-03-02T11:33:18-55644cf-fd2e1e7/linux-amd64-perf 2022-03-02T11:28:40-55644cf-bebe9aa/linux-amd64-longtest 2022-03-02T11:28:40-55644cf-bebe9aa/linux-amd64-perf 2022-03-02T11:27:34-55644cf-9f1239b/linux-amd64-perf 2022-03-01T23:49:01-55644cf-6da16b6/linux-amd64-longtest 2022-03-01T23:49:01-55644cf-6da16b6/linux-amd64-perf 2022-03-01T23:20:30-55644cf-aaa3d39/linux-amd64-longtest 2022-03-01T23:20:30-55644cf-aaa3d39/linux-amd64-perf 2022-03-01T22:02:33-55644cf-d40e7bb/linux-amd64-longtest 2022-03-01T22:02:33-55644cf-d40e7bb/linux-amd64-perf 2022-03-01T21:27:42-55644cf-b0db2f0/linux-amd64-longtest 2022-03-01T21:27:42-55644cf-b0db2f0/linux-amd64-perf 2022-03-01T20:52:30-55644cf-f4722d8/linux-amd64-longtest 2022-03-01T20:52:30-55644cf-f4722d8/linux-amd64-perf 2022-03-01T19:46:09-55644cf-d6d2ebb/linux-amd64-longtest 2022-03-01T19:46:09-55644cf-d6d2ebb/linux-amd64-perf 2022-03-01T19:45:51-55644cf-ad52356/linux-amd64-perf 2022-03-01T19:33:00-55644cf-258fc75/linux-amd64-longtest 2022-03-01T19:33:00-55644cf-258fc75/linux-amd64-perf 2022-03-01T18:48:36-55644cf-620a3c0/linux-amd64-longtest 2022-03-01T18:48:36-55644cf-620a3c0/linux-amd64-perf 2022-03-01T18:43:08-55644cf-510ad45/linux-amd64-longtest 2022-03-01T18:43:08-55644cf-510ad45/linux-amd64-perf 2022-03-01T18:13:15-55644cf-d9fd920/linux-amd64-longtest 2022-03-01T18:13:15-55644cf-d9fd920/linux-amd64-perf 2022-03-01T18:12:19-55644cf-d81464e/linux-amd64-perf 2022-03-01T07:36:46-55644cf-2199841/linux-amd64-longtest 2022-03-01T07:36:46-55644cf-2199841/linux-amd64-perf 2022-03-01T07:36:05-55644cf-7c151f3/linux-amd64-perf 2022-03-01T07:35:26-55644cf-6d881da/linux-amd64-perf 2022-03-01T06:01:28-55644cf-4f04e1d/linux-amd64-longtest 2022-03-01T06:01:28-55644cf-4f04e1d/linux-amd64-perf 2022-02-28T22:24:58-55644cf-936c7fb/linux-amd64-perf

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 20 (14 by maintainers)

Commits related to this issue

Most upvoted comments

I don’t think there’s any particular reason fixing this should be tied to the release cycle. I think putting it in Unreleased makes sense.