jjb: binutils-gdb: catch ERRORs in gdb.sum
authorSimon Marchi <simon.marchi@efficios.com>
Tue, 25 Apr 2023 18:28:47 +0000 (14:28 -0400)
committerMichael Jeanson <mjeanson@efficios.com>
Tue, 25 Apr 2023 20:12:03 +0000 (16:12 -0400)
commite9ba7f91e954218cd8fdaaa8e3cf8d2f6ddc80ed
tree706d907572c38c78456386bacbf8ad4f784b8c2a
parent8306891807c88241b56543a38dd074ba6f7eeaa2
jjb: binutils-gdb: catch ERRORs in gdb.sum

When tests encounter a fatal error, it is reported as:

    ERROR: blah blah blah

Unlike normal test result lines, they don't include the name of the .exp
file currently running.  It would still be nice to catch them and
consider them failures, as they are abnormal.  Update the Python gdb.sum
processing script to remember the name of the current .exp, by looking
at the "Running" lines.  And when it encounters an ERROR, generate a
junit failure.

Change-Id: If99d73992241370afe9a9b59cb9abe491272d05f
scripts/binutils-gdb/build.sh
This page took 0.023535 seconds and 4 git commands to generate.