From bc17b3a44ae17683c674f14c8d9b6a14dc66407d Mon Sep 17 00:00:00 2001 From: Tobias Werth Date: Fri, 28 Oct 2022 09:32:36 +0200 Subject: pkg/build: be more lenient when parsing Bazel's build log When Bazel is released with https://github.com/bazelbuild/bazel/commit/c9f9b0b84c486 the message on build failures changes. In general, we advise not to read the output but use the build protocol instead. --- pkg/build/build.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/build/build.go b/pkg/build/build.go index 4baed2b95..9f56976de 100644 --- a/pkg/build/build.go +++ b/pkg/build/build.go @@ -307,7 +307,7 @@ var buildFailureCauses = [...]buildFailureCause{ {weak: true, pattern: regexp.MustCompile(`: not found`)}, {weak: true, pattern: regexp.MustCompile(`: final link failed: `)}, {weak: true, pattern: regexp.MustCompile(`collect2: error: `)}, - {weak: true, pattern: regexp.MustCompile(`FAILED: Build did NOT complete`)}, + {weak: true, pattern: regexp.MustCompile(`(ERROR|FAILED): Build did NOT complete`)}, } var fileRes = []*regexp.Regexp{ -- cgit mrf-deployment