[gdb/testsuite] Remove unnecessary perror in some test-cases
authorTom de Vries <tdevries@suse.de>
Wed, 12 Oct 2022 14:50:16 +0000 (16:50 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 12 Oct 2022 14:50:16 +0000 (16:50 +0200)
commite2800454ce9d89f9c4587bc20ee7c6cd0122c340
tree6747974997d3d6652e810ebdef5514be63157cea
parent7fd882d4ad91916fd8a05148117f05ea9f5d756c
[gdb/testsuite] Remove unnecessary perror in some test-cases

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.
gdb/testsuite/gdb.dwarf2/fission-absolute-dwo.exp
gdb/testsuite/gdb.dwarf2/fission-relative-dwo.exp