espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-24 04:00:07 +08:00
Code Issues Packages Projects Releases Wiki Activity

[gdb/testsuite] Remove unnecessary perror in some test-cases

Browse Source 
On openSUSE Tumbleweed I noticed:
...
UNTESTED: gdb.dwarf2/fission-absolute-dwo.exp: fission-absolute-dwo.exp
ERROR: failed to compile fission-absolute-dwo
...

The ERROR is unnecessary, given that an UNTESTED is already emitted.

Furthermore, it could be argued that it is incorrect because it's not a
testsuite error to not be able to compile something, and UNTESTED or
UNSUPPORTED is more appropriate.

Remove the perror call, likewise in fission-relative-dwo.exp.

Tested on x86_64-linux.
This commit is contained in:
Tom de Vries
2022-10-12 16:50:16 +02:00
parent 7fd882d4ad
commit e2800454ce
2 changed files with 0 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
gdb/testsuite/gdb.dwarf2/fission-absolute-dwo.exp
View File

@ -112,7 +112,6 @@ set object_file [standard_output_file ${testfile}.o]
if { [build_executable_and_dwo_files "${testfile}.exp" ${binfile} {nodebug} \
[list $asm_file {nodebug split-dwo} ${object_file}] \
[list $srcfile {nodebug}]] } {
perror "failed to compile ${gdb_test_file_name}"
return -1
}

1
gdb/testsuite/gdb.dwarf2/fission-relative-dwo.exp
View File

@ -109,7 +109,6 @@ set object_file [standard_output_file ${testfile}.o]
if { [build_executable_and_dwo_files "${testfile}.exp" ${testfile} {nodebug} \
[list $asm_file {nodebug split-dwo} ${object_file}] \
[list $srcfile {nodebug}]] } {
perror "failed to compile ${gdb_test_file_name}"
return -1
}