This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on AIX-POWER7-plain, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Wed, 24 Jun 2015 11:34:57 -0400
- Subject: Failures on AIX-POWER7-plain, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
aix-power7-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/AIX-POWER7-plain/builds/19>
Commit(s) tested:
8371bf0cd99635c9eabed28481b34ea8934a948e
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/AIX-POWER7-plain/.git/tree/?h=master&id=8940e268e4461b5c5f65a5807487ffc8bc12fe45>
*** Regressions found ***
============================
new FAIL: gdb.threads/print-threads.exp: all threads ran once (fast) (total 4 threads ran)
new FAIL: gdb.threads/print-threads.exp: all threads ran once (slow with kill breakpoint) (total 3 threads ran)
new FAIL: gdb.threads/print-threads.exp: all threads ran once (slow) (total 4 threads ran)
new FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock off: signal command queries
new FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: second signal: signal command queries (the program is no longer running)
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: signal command does not query, signal delivered
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: stop with SIGUSR1
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: stop with SIGUSR2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: stepped thread under control
PASS -> FAIL: gdb.threads/stepi-random-signal.exp: continue to breakpoint: after pthread_kill
PASS -> FAIL: gdb.threads/tls.exp: continue to synch point
PASS -> FAIL: gdb.threads/tls.exp: continue to third thread
PASS -> FAIL: gdb.threads/tls.exp: third thread print me
new FAIL: gdb.threads/tls.exp: threads exited (the program exited)
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.threads/print-threads.exp: all threads ran once (fast) (total 4 threads ran)
new FAIL: gdb.threads/print-threads.exp: all threads ran once (slow with kill breakpoint) (total 3 threads ran)
new FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock off: signal command queries
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: signal command does not query, signal delivered
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: stop with SIGUSR1
PASS -> FAIL: gdb.threads/signal-command-multiple-signals-pending.exp: schedlock on: stop with SIGUSR2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: stepped thread under control
PASS -> FAIL: gdb.threads/stepi-random-signal.exp: continue to breakpoint: after pthread_kill
new FAIL: gdb.threads/thread-unwindonsignal.exp: continue until exit (the program is no longer running)
PASS -> FAIL: gdb.threads/tls.exp: continue to synch point
PASS -> FAIL: gdb.threads/tls.exp: continue to third thread
PASS -> FAIL: gdb.threads/tls.exp: third thread print me
new FAIL: gdb.threads/tls.exp: threads exited (the program exited)
============================