jjb: binutils-gdb: generate file with failures
authorSimon Marchi <simon.marchi@polymtl.ca>
Mon, 18 Jul 2022 18:35:41 +0000 (14:35 -0400)
committerSimon Marchi <simon.marchi@polymtl.ca>
Thu, 21 Jul 2022 16:12:53 +0000 (12:12 -0400)
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

index 828a09fce7746dcefa5e1e2ac80ef1da36d4a0a5..fb42965d8009a153f0419513473ef9dae770a7b7 100755 (executable)
@@ -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.
This page took 0.023385 seconds and 4 git commands to generate.