This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Wed, 11 Mar 2015 21:24:39 -0400
- Subject: Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
wildebeest-debian-wheezy-x86_64
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-x86_64-native-extended-gdbserver-m64/builds/433>
Commit(s) tested:
badd37cec86e705a190e501ab26975d352718619
Author(s) (in the same order as the commits):
Sergio Durigan Junior <sergiodj@redhat.com>
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-native-extended-gdbserver-m64/.git/tree/?h=master&id=45c4f86e62d269010b35ae51734d0db0e68ba89a>
*** Regressions found ***
============================
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the second fork (timeout)
new FAIL: gdb.trace/mi-traceframe-changed.exp: remote: continue to end (timeout)
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: trace stop
new FAIL: gdb.trace/mi-tsv-changed.exp: Can't run to main to check for trace support
new FAIL: gdb.trace/pending.exp: ftrace disconn: breakpoint on marker (got interactive prompt)
new FAIL: gdb.trace/pending.exp: ftrace disconn: continue to marker (the program exited)
PASS -> FAIL: gdb.trace/pending.exp: ftrace disconn: disconnect with pending tracepoint
new FAIL: gdb.trace/pending.exp: ftrace disconn: set pending tracepoint on set_point2 (timeout)
PASS -> FAIL: gdb.trace/pending.exp: ftrace disconn: start trace experiment
new FAIL: gdb.trace/pending.exp: ftrace installed_in_trace: continue to marker 2 (timeout)
new FAIL: gdb.trace/pending.exp: ftrace installed_in_trace: tfind test frame 0
new FAIL: gdb.trace/unavailable.exp: unavailable locals: static locals: tsave unavailable.locals.tfile (timeout)
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.gdb/python-selftest.exp: call catch_command_errors(execute_command, "python print(5)", 0)
new FAIL: gdb.threads/watchpoint-fork.exp: parent: multithreaded: breakpoint (A) after the second fork (timeout)
new FAIL: gdb.trace/mi-traceframe-changed.exp: remote: continue to end (timeout)
PASS -> FAIL: gdb.trace/mi-traceframe-changed.exp: remote: trace stop
new FAIL: gdb.trace/mi-tsv-changed.exp: Can't run to main to check for trace support
new FAIL: gdb.trace/pending.exp: ftrace disconn: breakpoint on marker (got interactive prompt)
new FAIL: gdb.trace/pending.exp: ftrace disconn: continue to marker (the program exited)
PASS -> FAIL: gdb.trace/pending.exp: ftrace disconn: disconnect with pending tracepoint
new FAIL: gdb.trace/pending.exp: ftrace disconn: set pending tracepoint on set_point2 (timeout)
PASS -> FAIL: gdb.trace/pending.exp: ftrace disconn: start trace experiment
new FAIL: gdb.trace/pending.exp: ftrace installed_in_trace: continue to marker 2 (timeout)
new FAIL: gdb.trace/pending.exp: ftrace installed_in_trace: tfind test frame 0
new FAIL: gdb.trace/unavailable.exp: unavailable locals: static locals: tsave unavailable.locals.tfile (timeout)
============================
*** Failures that are being ignored ***
============================
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
FAIL: gdb.dwarf2/gdb-index.exp: touch binary
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call============================