This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on RHEL-s390x-m64, branch gdb-8.3-branch
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Sat, 02 Mar 2019 09:32:34 -0500
- Subject: Failures on RHEL-s390x-m64, branch gdb-8.3-branch
Buildslave:
rhel-7_1-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/RHEL-s390x-m64/builds/9357>
Commit(s) tested:
4344b2225c8d4878a27401b94ec6315c728f46bf
Author(s) (in the same order as the commits):
Eli Zaretskii <eliz@gnu.org>
Subject:
Avoid compilation warnings on MinGW.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/RHEL-s390x-m64/43/4344b2225c8d4878a27401b94ec6315c728f46bf/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/siginfo-thread.exp: extract si_errno
new FAIL: gdb.python/python.exp: set the hook
PASS -> FAIL: gdb.python/python.exp: set the hook to default
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=10: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=17: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=1: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=4: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=0: inferior 1 exited
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.