https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88002
Bug ID: 88002
Summary: libbacktrace and libiberty tests don't use dejagnu
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When grepping "make check" output, we find a number of passes:
...
$ grep ^PASS CHECKLOG
PASS: test-expandargv-0.
PASS: test-expandargv-1.
PASS: test-expandargv-2.
PASS: test-expandargv-3.
PASS: test-expandargv-4.
PASS: test-expandargv-5.
PASS: test-expandargv-6.
PASS: test-strtol-0.
PASS: test-strtol-1.
PASS: test-strtol-2.
PASS: test-strtol-3.
PASS: test-strtol-4.
PASS: test-strtol-5.
PASS: test-strtol-6.
PASS: test-strtol-7.
PASS: test-strtol-8.
PASS: test-strtol-9.
PASS: test-strtol-10.
PASS: test-strtol-11.
PASS: test-strtol-12.
PASS: test-strtol-13.
PASS: test-strtol-14.
PASS: test-strtol-15.
PASS: test-strtol-16.
PASS: test-strtol-17.
PASS: test-strtol-18.
PASS: test-strtol-19.
PASS: test-strtol-20.
PASS: btest
PASS: edtest
PASS: stest
PASS: ctestg
PASS: ctesta
PASS: dtest
PASS: ttest
PASS: btest
PASS: stest
PASS: ztest
PASS: edtest
PASS: ztest
PASS: ctestg
PASS: ttest
PASS: ctesta
...
The passes come from the test suites of libiberty and libbacktrace, which are
not using dejagnu.
Consequently the PASS/FAILs are not included in any .sum files, so when
comparing test results using .sum files, a regression in these tests will go
unnoticed.
Also, a consequence of not using dejagnu is that RUNTESTFLAGS are ignored.
[ Btw, note that the libbacktrace tests (btest etc) are run twice, once for
build/libbacktrace and once for build/<target>/libbacktrace. ]
