This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Fedora-x86_64-cc-with-index, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Wed, 29 Jul 2015 10:43:45 -0400
- Subject: Failures on Fedora-x86_64-cc-with-index, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/1524>
Commit(s) tested:
452397af30f68f6d4ed05fa6d9fc30ca70cbe7f9
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-cc-with-index/.git/tree/?h=master&id=6a8d10149f51dfa66e4c54717fefd8550c85b5f6>
*** Regressions found ***
============================
new FAIL: gdb.base/corefile.exp: core-file warning-free
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================
*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/corefile.exp: core-file warning-free
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
new FAIL: gdb.cp/inherit.exp: print g_vD
new FAIL: gdb.cp/inherit.exp: print g_vE
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype ee
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype ee
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype ee
PASS -> FAIL: gdb.cp/virtbase.exp: print *(D *) e
PASS -> FAIL: gdb.cp/virtbase.exp: print *this
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.fortran/library-module.exp: print var_i in lib
PASS -> FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (3)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (3)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: step into finish marker
PASS -> FAIL: gdb.opt/inline-locals.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-locals.exp: backtrace from bar (3)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (3)
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
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-next over solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: run until end part two
new FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end (timeout)
============================
*** Failures that are being ignored ***
============================
============================