From ca14bc89c07f9ccf4e07e7d20fb3c8be22245823 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Mon, 1 Apr 2019 14:23:09 +0200 Subject: 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. --- pkg/build/gvisor.go | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 { -- cgit mrf-deployment