diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2019-03-29 11:00:34 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2019-03-29 11:00:34 +0100 |
| commit | 9633c5c8a1a030cdfdc0f94ae460314c7fc15faa (patch) | |
| tree | 01efde3d54f1261007510e6662045f07f1621cd2 /pkg/build/openbsd.go | |
| parent | 6b138f0f3ced97b0260f6253874d7c84c6408662 (diff) | |
pkg/build: extract bazel build errors
We currently manually call extractRootCause in few selected places
to denote kernel build errors that we want to report to developers.
The rest are considered infra errors that we don't report.
This does not work well. We are missing fuchsia and gvisor build errors.
Treat all external command exection failures as kernel build errors instead.
Let's see how this works in practice.
Also add bazel-specfic error patterns and tests.
Diffstat (limited to 'pkg/build/openbsd.go')
| -rw-r--r-- | pkg/build/openbsd.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pkg/build/openbsd.go b/pkg/build/openbsd.go index 24bd7a7d4..49c78c6d0 100644 --- a/pkg/build/openbsd.go +++ b/pkg/build/openbsd.go @@ -35,7 +35,7 @@ func (ctx openbsd) build(targetArch, vmType, kernelDir, outputDir, compiler, use } for _, tgt := range []string{"clean", "obj", "config", "all"} { if err := ctx.make(compileDir, tgt); err != nil { - return extractRootCause(err) + return err } } for _, s := range []struct{ dir, src, dst string }{ |
