Failures on Debian-s390x-m64, branch master
sergiodj+buildbot@redhat.com
sergiodj+buildbot@redhat.com
Wed Jul 29 03:58:00 GMT 2015
Buildslave:
debian-wheezy-s390x-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-s390x-m64/builds/246>
Commit(s) tested:
11509220a045532b1995b4af5dac2f921b541003
Author(s) (in the same order as the commits):
Hans-Peter Nilsson <hp@bitrange.com>
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-s390x-m64/.git/tree/?h=master&id=e3b44988660e851d126c469435b0b35123f2c28c>
*** Regressions found ***
============================
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tld
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: finish shows vector return value
new FAIL: gdb.base/gnu_vector.exp: verify vector return value (the program exited)
new FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)
new FAIL: gdb.base/longjmp.exp: next over longjmp(1)
new FAIL: gdb.cp/annota2.exp: annotate-quit
new FAIL: gdb.cp/annota2.exp: watch triggered on a.x (timeout)
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at catch <<2>>
new FAIL: gdb.cp/exceptprint.exp: int: print exception value at throw <<2>>
new FAIL: gdb.cp/exceptprint.exp: reference to struct: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: string: print exception value at catch
new FAIL: gdb.cp/exceptprint.exp: struct: print exception value at catch
new FAIL: gdb.cp/inherit.exp: print g_vD
new FAIL: gdb.cp/inherit.exp: print g_vE
new FAIL: gdb.cp/virtbase.exp: print *(D *) e
new FAIL: gdb.cp/virtbase.exp: print *this
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.go/methods.exp: setting breakpoint at (*main.T).Bar
new FAIL: gdb.go/methods.exp: setting breakpoint at main.T.Foo
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
PASS -> FAIL: gdb.python/py-objfile.exp: Add separate debug file file
PASS -> FAIL: gdb.python/py-objfile.exp: Get no-debug objfile file
PASS -> FAIL: gdb.python/py-objfile.exp: Test owner of real objfile.
PASS -> FAIL: gdb.python/py-objfile.exp: Test owner of separate debug file
PASS -> FAIL: gdb.python/py-objfile.exp: Test user-name of owner of separate debug file
new FAIL: gdb.python/py-objfile.exp: print lookup_objfile of separate debug file
PASS -> FAIL: gdb.python/py-objfile.exp: print main with debug info
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 test forced_stabs
new FAIL: gdb.stabs/gdb11479.exp: Inspect t in test2 forced_stabs
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
new FAIL: gdb.trace/tfile.exp: tfind 0 on trace file
============================
More information about the Gdb-testers
mailing list