public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: Failures on Fedora-x86_64-native-extended-gdbserver-m64
Date: Thu, 15 Jan 2015 00:32:00 -0000	[thread overview]
Message-ID: <E1YBYE4-0005vO-2J@kwanyin.sergiodj.net> (raw)

Builder:
	fedora-x86-64-1
Commit(s) tested:
	c36094316505cf2628812e520b08eb42c0299613
Log URL(s):
	<http://gdb-build.sergiodj.net:8010/results/Fedora-x86_64-native-extended-gdbserver-m64/c36094316505cf2628812e520b08eb42c0299613>
Author(s) (in the same order as the commits):
	GDB Administrator <gdbadmin@sourceware.org>

============================
new FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: set breakpoint always-inserted off
new FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 2: attach (timeout)
new FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 3: attach (got interactive prompt)
============================




             reply	other threads:[~2015-01-15  0:32 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  0:32 buildbot [this message]
2015-01-15  2:21 buildbot
2015-01-15  3:54 buildbot
2015-01-15  9:35 buildbot
2015-01-15 10:51 buildbot
2015-01-15 11:48 buildbot
2015-01-15 13:42 buildbot
2015-01-15 16:56 buildbot
2015-01-15 18:42 buildbot
2015-01-15 19:32 buildbot
2015-01-15 20:47 buildbot
2015-01-16  0:30 buildbot
2015-01-16  6:12 buildbot
2015-01-16 11:55 buildbot
2015-01-16 15:10 buildbot
2015-01-16 16:16 buildbot
2015-01-16 16:46 buildbot
2015-01-16 16:55 buildbot
2015-01-16 18:26 buildbot
2015-01-17  0:32 buildbot
2015-01-17 13:59 buildbot
2015-01-17 17:12 buildbot
2015-01-18  0:32 buildbot
2015-01-19  0:59 sergiodj
2015-01-19  8:40 sergiodj
2015-01-19 11:10 sergiodj
2015-01-19 13:48 sergiodj
2015-01-19 16:38 sergiodj
2015-01-19 17:32 sergiodj
2015-01-19 17:33 sergiodj
2015-01-19 19:30 sergiodj
2015-01-20  2:47 sergiodj
2015-01-20  5:15 sergiodj
2015-01-20  9:59 sergiodj
2015-01-20 10:30 sergiodj
2015-01-20 11:37 sergiodj
2015-01-20 14:14 sergiodj
2015-01-20 15:44 sergiodj
2015-01-20 22:34 ` Sergio Durigan Junior
2015-01-20 16:54 sergiodj
2015-01-20 17:48 sergiodj
2015-01-20 19:38 sergiodj
2015-01-20 20:02 sergiodj
2015-01-21  0:59 sergiodj
2015-01-21 16:25 sergiodj
2015-01-21 16:57 sergiodj
2015-01-21 17:24 ` Sergio Durigan Junior
2015-01-21 18:05 sergiodj
2015-01-22  1:13 sergiodj
2015-01-22  6:26 sergiodj
2015-01-22 13:49 sergiodj
2015-01-22 16:24 sergiodj
2015-01-22 21:29 sergiodj
2015-01-22 23:08 sergiodj
2015-01-22 23:25 sergiodj
2015-01-23  8:14 sergiodj
2015-01-23 16:43 sergiodj
2015-01-23 18:10 sergiodj
2015-01-23 18:11 sergiodj
2015-01-24  0:06 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=E1YBYE4-0005vO-2J@kwanyin.sergiodj.net \
    --to=buildbot@sergiodj.net \
    --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).