This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Debian-x86_64-m64, branch gdb-7.12-branch
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Tue, 23 Aug 2016 18:59:20 -0400
- Subject: Failures on Debian-x86_64-m64, branch gdb-7.12-branch
- Authentication-results: sourceware.org; auth=none
Buildslave:
wildebeest-debian-wheezy-x86_64
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-x86_64-m64/builds/3935>
Commit(s) tested:
7157552b0f8b4bb74910d85808244029c89229ff
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Subject:
x32 Fast tracepoints: IPA target descriptions
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-m64/.git/tree/?h=gdb-7.12-branch&id=d05b5d8c0dd30bc0c4ad8fdd3b9893887fc8d39e>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: detach
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 2: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 2: detach
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 3: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: fg attach 3: detach
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 1: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 1: detach
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 2: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 2: detach
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 3: info threads shows two LWPs
PASS -> FAIL: gdb.threads/clone-attach-detach.exp: bg attach 3: detach
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.