From c0e55ab2468da9e8b215d77f31d07c6f14bd4377 Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Mon, 18 Jul 2022 14:35:41 -0400 Subject: [PATCH] jjb: binutils-gdb: generate file with failures Generate the "gdb.fail.sum" file, containing the failures that have caused the build to fail. This is a bit nicer to read than the converted JUnit summary parsed by Jenkins, as it's in the usual ".sum" format GDB developers are used to. Change-Id: Id71304b1d51a55fdd4fe3072abd6f97ceaa34970 --- scripts/binutils-gdb/build.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/binutils-gdb/build.sh b/scripts/binutils-gdb/build.sh index 828a09f..fb42965 100755 --- a/scripts/binutils-gdb/build.sh +++ b/scripts/binutils-gdb/build.sh @@ -624,6 +624,7 @@ EOF known_failures_file="known-failures-${target_board}" grep --invert-match --fixed-strings --file="$known_failures_file" "${WORKSPACE}/results/gdb.sum" > "${WORKSPACE}/results/gdb.filtered.sum" +grep --extended-regexp --regexp="^(FAIL|XPASS|UNRESOLVED|DUPLICATE):" "${WORKSPACE}/results/gdb.filtered.sum" > "${WORKSPACE}/results/gdb.fail.sum" || true # For informational purposes: check if some known failure lines did not appear # in the gdb.sum. -- 2.34.1