From: Dennis Clarke <dclarke@blastwave.org>
To: GDB <gdb@sourceware.org>
Subject: Very messy results from testsuite in GDB 8.1
Date: Mon, 05 Feb 2018 20:06:00 -0000 [thread overview]
Message-ID: <f30e9ff0-7d7b-e851-98a1-fee90dd217ce@blastwave.org> (raw)
I was saddened to see these results of the 8.1 testsuite :
=== gdb Summary ===
# of expected passes 48036
# of unexpected failures 881
# of unexpected successes 2
# of expected failures 56
# of unknown successes 4
# of known failures 66
# of unresolved testcases 11
# of untested testcases 50
# of unsupported tests 213
/usr/local/build/gdb-8.1_4.13.0-1-powerpc64.001/gdb/gdb version 8.1 -nw
-nx -data-directory
/usr/local/build/gdb-8.1_4.13.0-1-powerpc64.001/gdb/testsuite/../data-directory
This is an order of magnitude worse than a previous build for 8.0.1 :
=== gdb Summary ===
# of expected passes 33093
# of unexpected failures 96
# of expected failures 58
# of known failures 65
# of unresolved testcases 3
# of untested testcases 56
# of unsupported tests 206
/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite/../../gdb/gdb
version 8.0.1 -nw -nx -data-directory
/usr/local/build/gdb-8.0.1_linux_3.16.0-4-powerpc64.001/gdb/testsuite/../data-directory
Of course the kernel rev has changed since then, considerably, as well
as a number of tools in the system. Nearly 900 unexpected test failures
is quite distressing. Certainly not a usable resultant binary.
There are a number of internal errors :
-bash-4.4$ grep "^FAIL" ../gdb-8.1_4.13.0-1-powerpc64.001.check.log |
grep "internal error"
FAIL: gdb.base/multi-forks.exp: detach 2 (GDB internal error)
FAIL: gdb.base/multi-forks.exp: detach 3 (GDB internal error)
FAIL: gdb.base/multi-forks.exp: detach 4 (GDB internal error)
FAIL: gdb.base/multi-forks.exp: detach 5 (GDB internal error)
FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process:
detach: detach: detach child (GDB internal error)
FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process:
detach: watchpoint: detach child (GDB internal error)
FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process:
continue: detach: detach child (GDB internal error)
FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process:
continue: watchpoint: detach child (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded:
breakpoint after the first fork (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded:
breakpoint after the second fork (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint
(A) after the first fork (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint
after the first fork (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint
after the first fork (GDB internal error)
FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint
(A) after the first fork (GDB internal error)
I will move onwards to a Red Hat Enterprise Linux 7.4 system and see
what results happen there but for the moment I have to ask if other
people are seeing reasonable build and testsuite results?
Dennis Clarke
next reply other threads:[~2018-02-05 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:06 Dennis Clarke [this message]
2018-02-05 22:20 ` Yao Qi
2018-02-05 22:40 ` Dennis Clarke
2018-02-06 4:18 ` Joel Brobecker
2018-02-06 18:15 ` Dennis Clarke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f30e9ff0-7d7b-e851-98a1-fee90dd217ce@blastwave.org \
--to=dclarke@blastwave.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox