This is the mail archive of the gdb-testers@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Failures on Debian-i686-native-gdbserver, branch master


Buildslave:
	wildebeest-debian-wheezy-i686

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Debian-i686-native-gdbserver/builds/197>

Commit(s) tested:
	9035ed511099fd79bc5a76d1ac457c0a8226a324

Author(s) (in the same order as the commits):
	Mike Frysinger <vapier@gentoo.org>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-i686-native-gdbserver/.git/tree/?h=master&id=4cc6c96e7345ac7cd4fad29d048a2e1860f258de>

*** Regressions found ***
============================
new FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=4: thread 1 restarted
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.arch/i386-biarch-core.exp: .text is readable
new FAIL: gdb.arch/i386-biarch-core.exp: core-file
new FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=4: thread 1 restarted
============================


*** Failures that are being ignored ***
============================
FAIL: gdb.ada/mi_var_array.exp: list vta's children
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call
FAIL: gdb.base/longjmp.exp: next over patt3
FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=2: thread 10 broke out of loop (timeout)
FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=2: thread 11 broke out of loop (timeout)
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
============================




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]