This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Fedora-s390x-m64, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Fri, 14 Aug 2015 08:46:24 -0400
- Subject: Failures on Fedora-s390x-m64, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
marist-fedora-s390x
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-s390x-m64/builds/1303>
Commit(s) tested:
f8edc4ff051b4e29997681cb3bc9078d98f4d457
Author(s) (in the same order as the commits):
Matthew Fortune <matthew.fortune@imgtec.com>
Subject:
Add myself to gdb MAINTAINERS
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Fedora-s390x-m64/.git/tree/?h=master&id=4267498120d0b1e94c7c2377337467e65ac16406>
*** Regressions found ***
============================
PASS -> FAIL: gdb.base/siginfo-thread.exp: Extract si_errno
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.base/gnu_vector.exp: finish shows vector return value
new FAIL: gdb.base/gnu_vector.exp: verify vector return value (the program exited)
PASS -> FAIL: gdb.base/siginfo-thread.exp: Extract si_errno
PASS -> FAIL: gdb.python/py-lookup-type.exp: lookup type ucent using language d
PASS -> FAIL: gdb.server/non-existing-program.exp: gdbserver exits cleanly
new FAIL: gdb.threads/signal-while-stepping-over-bp-other-thread.exp: step (pattern 3)
PASS -> FAIL: gdb.threads/watchthreads.exp: threaded watch loop
PASS -> FAIL: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: tfile: tfind 0 again
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: tfile: -trace-find frame-number 0
============================
*** Failures that are being ignored ***
============================
FAIL: gdb.base/async-shell.exp: process stopped (timeout)
============================