aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/build/gvisor.go
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2019-04-01 14:23:09 +0200
committerDmitry Vyukov <dvyukov@google.com>2019-04-01 14:23:09 +0200
commitca14bc89c07f9ccf4e07e7d20fb3c8be22245823 (patch)
tree18d40352541761521b13679c6ddc6bd5bb5bb674 /pkg/build/gvisor.go
parent9e381a42d3a390c0e1f4935cdd41a59ffdd15b71 (diff)
pkg/build: increase gvosir build timeout
The 1 hour timeout is quite high. But we've seen false positives with 20 mins on the first build after bazel/deps update. Also other gvisor instances running on the same machine contribute to longer build times.
Diffstat (limited to 'pkg/build/gvisor.go')
-rw-r--r--pkg/build/gvisor.go5
1 files changed, 4 insertions, 1 deletions
diff --git a/pkg/build/gvisor.go b/pkg/build/gvisor.go
index a2a856dd8..6db9e6ab6 100644
--- a/pkg/build/gvisor.go
+++ b/pkg/build/gvisor.go
@@ -27,7 +27,10 @@ func (gvisor gvisor) build(targetArch, vmType, kernelDir, outputDir, compiler, u
outBinary = "bazel-bin/runsc/linux_amd64_pure_stripped/runsc"
}
outBinary = filepath.Join(kernelDir, filepath.FromSlash(outBinary))
- if _, err := osutil.RunCmd(20*time.Minute, kernelDir, compiler, args...); err != nil {
+ // The 1 hour timeout is quite high. But we've seen false positives with 20 mins
+ // on the first build after bazel/deps update. Also other gvisor instances running
+ // on the same machine contribute to longer build times.
+ if _, err := osutil.RunCmd(60*time.Minute, kernelDir, compiler, args...); err != nil {
return err
}
if err := osutil.CopyFile(outBinary, filepath.Join(outputDir, "image")); err != nil {