This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Very messy results from testsuite in GDB 8.1



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











Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]