public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Failures on Debian-x86_64-native-gdbserver-m64
Date: Tue, 20 Jan 2015 13:38:00 -0000 [thread overview]
Message-ID: <E1YDWzH-0005LQ-Ki@kwanyin.sergiodj.net> (raw)
Buildslave:
wildebeest-debian-wheezy-x86_64
Commit(s) tested:
3e2b0f3116a46c8a9a6ffbcb5ae4847b6601467a
23283c1be02de06666e4d934b1fc499c0d72f9c2
43d66c95c826441c64bacfa07095535ddea57a51
c05b575a8dfabab6af5d8586d1a5c0c67f819ac2
Log URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-native-gdbserver-m64/.git/tree/?id=00f7444f34688b31636f0b8213a49297465d0693>
Author(s) (in the same order as the commits):
Alan Modra <amodra@gmail.com>
Alan Modra <amodra@gmail.com>
Andrew Burgess <andrew.burgess@embecosm.com>
Andrew Burgess <andrew.burgess@embecosm.com>
============================
PASS -> FAIL: gdb.dwarf2/gdb-index.exp: touch binary
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 1 out of 80 on watched_data (timeout)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 2 out of 80 on watched_data (timeout)
new FAIL: gdb.threads/wp-replication.exp: Thread 9 hit breakpoint at thread_started (timeout)
new FAIL: gdb.threads/wp-replication.exp: set var test_ready=1 (timeout)
============================
next reply other threads:[~2015-01-20 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 13:38 sergiodj [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-23 18:24 sergiodj
2015-01-23 11:24 sergiodj
2015-01-23 1:03 sergiodj
2015-01-20 16:36 sergiodj
2015-01-21 0:33 ` Sergio Durigan Junior
2015-01-20 9:56 sergiodj
2015-01-20 7:47 sergiodj
2015-01-20 1:55 sergiodj
2015-01-19 19:08 sergiodj
2015-01-19 16:03 sergiodj
2015-01-19 11:44 sergiodj
2015-01-19 9:07 sergiodj
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=E1YDWzH-0005LQ-Ki@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: link
Be 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).