public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-testers@sourceware.org
Subject: Re: Failures on Fedora-x86_64-native-gdbserver-m64
Date: Mon, 19 Jan 2015 18:24:00 -0000 [thread overview]
Message-ID: <87mw5ews4d.fsf@redhat.com> (raw)
In-Reply-To: <E1YDG36-0003IR-EW@kwanyin.sergiodj.net> (sergiodj@redhat.com's message of "Mon, 19 Jan 2015 12:23:36 -0500")
On Monday, January 19 2015, I wrote:
> Buildslave:
> fedora-x86-64-2
> Commit(s) tested:
> 1f99f6d0689d20db44c0c7d88e8af1ebe900d187
> 63413d85873c450fa4ed2494f21fb1a65bdaf554
> 3e2aa5bbd36be9cf63530e5db2f6cf3898762a22
> Log URL(s):
> <Error fetching commit ID for 3e2aa5bbd36be9cf63530e5db2f6cf3898762a22>
> Author(s) (in the same order as the commits):
> Joel Brobecker <brobecker@adacore.com>
> Eli Zaretskii <eliz@gnu.org>
> H.J. Lu <hjl.tools@gmail.com>
>
> ============================
> ============================
Sourceware imposed load average restrictions on the git:// protocol,
which caused errors on this and the following builds. I talked to Frank
and he made some adjustments on sourceware; let's see how it goes.
Meanwhile, I triggered a rebuild for all the builds affected.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-01-19 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 17:32 sergiodj
2015-01-19 18:24 ` Sergio Durigan Junior [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-23 11:44 sergiodj
2015-01-22 20:11 sergiodj
2015-01-20 11:23 sergiodj
2015-01-16 19:22 buildbot
2015-01-16 17:02 buildbot
2015-01-16 16:43 buildbot
2015-01-16 1:25 buildbot
2015-01-16 17:03 ` Sergio Durigan Junior
2015-01-15 20:34 buildbot
2015-01-15 17:49 buildbot
2015-01-15 12:43 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=87mw5ews4d.fsf@redhat.com \
--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).