public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj@redhat.com To: gdb-testers@sourceware.org Subject: Failures on Fedora-x86_64-native-gdbserver-m32 Date: Thu, 22 Jan 2015 05:40:00 -0000 [thread overview] Message-ID: <E1YE6Bq-0001Qi-DG@kwanyin.sergiodj.net> (raw) Buildslave: fedora-x86-64-2 Commit(s) tested: b99e251379fd81716660e88b933f0bc015d6c6d8 Author(s) (in the same order as the commits): GDB Administrator <gdbadmin@sourceware.org> Log URL(s): <http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-native-gdbserver-m32/.git/tree/?id=a9a6c9c28bf57f899c6e29338f46470c3098f223> *** Failed to make TAGS *** Log URL: http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/37/steps/make%20tags/logs/stdio *** Regressions found *** ============================ new FAIL: gdb.threads/print-threads.exp: all threads ran once <<2>> ============================ Failures that are being ignored: FAIL: gdb.ada/interface.exp: print s FAIL: gdb.ada/iwide.exp: print My_Drawable FAIL: gdb.ada/iwide.exp: print d_access.all FAIL: gdb.ada/iwide.exp: print dp_access.all FAIL: gdb.ada/iwide.exp: print s_access.all FAIL: gdb.ada/iwide.exp: print sp_access.all FAIL: gdb.ada/mi_interface.exp: Create ggg1 varobj FAIL: gdb.ada/mi_interface.exp: list ggg1's children FAIL: gdb.ada/ptype_tagged_param.exp: ptype s FAIL: gdb.ada/str_uninit.exp: print my_str FAIL: gdb.ada/tagged.exp: print obj FAIL: gdb.ada/tagged.exp: ptype obj FAIL: gdb.ada/tagged_access.exp: ptype c.all FAIL: gdb.ada/tagged_access.exp: ptype c.menu_name FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call FAIL: gdb.base/random-signal.exp: stop with control-c (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: breakpoint on thread_function0's caller (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: delete 5 (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: let local watchpoint trigger (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: let thread_function0 return (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint automatically deleted (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint is still in breakpoint list (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint still triggers (timeout) FAIL: gdb.threads/local-watch-wrong-thread.exp: the other thread stopped on breakpoint (timeout)
next reply other threads:[~2015-01-22 1:13 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-22 5:40 sergiodj [this message] -- strict thread matches above, loose matches on Subject: below -- 2015-01-23 16:43 sergiodj 2015-01-23 0:03 sergiodj 2015-01-22 7:53 sergiodj 2015-01-21 17:23 sergiodj 2015-01-21 12:14 sergiodj 2015-01-21 2:31 sergiodj 2015-01-20 15:39 sergiodj 2015-01-20 5:31 sergiodj 2015-01-19 17:33 sergiodj 2015-01-19 17:32 sergiodj 2015-01-19 10:00 sergiodj 2015-01-18 1:11 buildbot 2015-01-19 0:32 ` Sergio Durigan Junior 2015-01-17 14:37 buildbot 2015-01-16 17:01 buildbot 2015-01-16 16:40 buildbot 2015-01-16 6:52 buildbot 2015-01-16 1:09 buildbot 2015-01-16 17:03 ` Sergio Durigan Junior 2015-01-15 21:37 buildbot 2015-01-15 20:14 buildbot 2015-01-15 17:32 buildbot 2015-01-15 14:18 buildbot 2015-01-15 12:26 buildbot 2015-01-15 10:06 buildbot
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=E1YE6Bq-0001Qi-DG@kwanyin.sergiodj.net \ --to=sergiodj@redhat.com \ --cc=gdb-testers@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).