Failures on Debian-s390x-m64, branch master
sergiodj+buildbot@redhat.com
sergiodj+buildbot@redhat.com
Fri Dec 18 20:21:00 GMT 2015
Buildslave:
debian-wheezy-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-m64/builds/1367>
Commit(s) tested:
aff9c0f8ab32e4f2f7ff9700afe84a61d23a08c6
Author(s) (in the same order as the commits):
Simon Marchi <simon.marchi@ericsson.com>
Subject:
Add documentation to gdb_compile
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-s390x-m64/.git/tree/?h=master&id=7da3383fa2040b38b87f0cb6005546462826e3ac>
*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/watchthreads.exp: threaded watch loop
PASS -> FAIL: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30
============================
*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/s390-multiarch.exp: compile (31)
new FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tld
new FAIL: gdb.base/catch-syscall.exp: mid-vfork: syscall vfork has returned
new FAIL: gdb.base/corefile.exp: core-file warning-free
new FAIL: gdb.base/dfp-test.exp: Correct _Decimal128 return value from called function.
new FAIL: gdb.base/gnu_vector.exp: verify vector return value
new FAIL: gdb.base/longjmp.exp: next over longjmp(1)
new FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)
new FAIL: gdb.cp/exceptprint.exp: string: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: struct: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: reference to struct: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at throw <<2>>
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at catch <<2>>
new FAIL: gdb.dwarf2/dw2-anon-mptr.exp: ptype crash
new FAIL: gdb.dwarf2/implptrpiece.exp: print/d p[-1]
new FAIL: gdb.dwarf2/member-ptr-forwardref.exp: ptype c
new FAIL: gdb.linespec/explicit.exp: complete unique function name (timeout)
new FAIL: gdb.linespec/explicit.exp: complete non-unique function name (timeout)
new FAIL: gdb.linespec/explicit.exp: complete non-existant function name (timeout)
new FAIL: gdb.linespec/explicit.exp: complete unique file name (timeout)
new FAIL: gdb.linespec/explicit.exp: complete non-unique file name (timeout)
new FAIL: gdb.mi/pr11022.exp: data-write-memory-bytes &x "01": watchpoint hit 2 (unknown output after running)
new FAIL: gdb.modula2/unbounded-array.exp: print unbounded array contents
new FAIL: gdb.opt/solib-intra-step.exp: second-hit
new FAIL: gdb.python/py-value-cc.exp: u's second field via field
PASS -> FAIL: gdb.server/non-existing-program.exp: gdbserver exits cleanly
new FAIL: gdb.stabs/gdb11479.exp: Inspect t in test2 forced_stabs
new FAIL: gdb.stabs/gdb11479.exp: Inspect t in test forced_stabs
PASS -> FAIL: gdb.threads/watchthreads.exp: threaded watch loop
PASS -> FAIL: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30
new FAIL: gdb.trace/tfile.exp: tfind 0 on trace file
============================
More information about the Gdb-testers
mailing list