This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Debian-i686, branch gdb-7.12-branch
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Wed, 10 Aug 2016 11:55:18 -0400
- Subject: Failures on Debian-i686, branch gdb-7.12-branch
- Authentication-results: sourceware.org; auth=none
Buildslave:
wildebeest-debian-wheezy-i686
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-i686/builds/3946>
Commit(s) tested:
9be00a778d646d92b7940d74425b58d93cb73d0d
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Subject:
Quiet ARI gettext checks
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-i686/.git/tree/?h=gdb-7.12-branch&id=60c33e679ba6f978d6d624814527f156b2a33bdf>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: step: step
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr1: continue to sigusr1_handler
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.