This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Fedora-ppc64le-native-extended-gdbserver-m64, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Tue, 24 Mar 2015 04:47:59 -0400
- Subject: Failures on Fedora-ppc64le-native-extended-gdbserver-m64, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
fedora-21-ppc64le-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-ppc64le-native-extended-gdbserver-m64/builds/438>
Commit(s) tested:
64dd13dfc267b1d13f42519f220e89a4386591fd
Author(s) (in the same order as the commits):
Mike Frysinger <vapier@gentoo.org>
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Fedora-ppc64le-native-extended-gdbserver-m64/.git/tree/?h=master&id=268bfbdaf11434a5e2c8f2a364b5a9c51aa89c1f>
*** Regressions found ***
============================
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: finish
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: hardware breakpoints work
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: multithreaded watchpoints work at A
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: multithreaded watchpoints work at B
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: singlethread watchpoints work
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint A after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint A after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint B after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: watchpoint B after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: finish
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: hardware breakpoints work
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoint after the first fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoint after the second fork
new FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: watchpoints work
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.gdb/python-selftest.exp: call catch_command_errors(execute_command, "python print(5)", 0)
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 2
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 3
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 4
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 5
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 2
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 3
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 4
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 5
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================
*** Failures that are being ignored ***
============================
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
FAIL: gdb.threads/fork-thread-pending.exp: 1, get to the fork event (timeout)
FAIL: gdb.threads/fork-thread-pending.exp: 1, multiple threads found (the program exited)
============================