From: David Engster <deng@randomsample.de>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [Buildbot] Gnus build failed
Date: Sun, 31 May 2015 12:44:17 +0200 [thread overview]
Message-ID: <87wpzpni0u.fsf@isaac.fritz.box> (raw)
In-Reply-To: <b4mbnh4jl4p.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 29 May 2015 09:13:58 +0900")
Katsumi Yamaoka writes:
> On Fri, 29 May 2015 01:57:05 +0200, gnus-buildbot@randomsample.de wrote:
>> The Buildbot has detected a new failure on builder emacs-devel.
>> Details at: http://randomsample.de/gnus-buildbot/builders/emacs-devel/builds/737
>> Blamelist: Katsumi Yamaoka <yamaoka@jpl.org>
>
>
>> Please note:
>> - The Buildbot uses 'make fail-on-warn'
>> - If this build fails again, it will only be reported on the
>> Gnus-buildbot mailing list (gmane.emacs.gnus.buildbot)
>
>> ---------------------------------------------------------------
>
> Why did the build, in the last process `test', fail?
> The change are for only string objects (see below), so it should
> not be a cause of any error.
Two reasons, and both indeed have nothing to do with the actual commit:
- Using `sleep-for' to wait for the ping to Gmane does not seem to
wait. This seems to be this issue here:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15990
http://lists.gnu.org/archive/html/emacs-devel/2013-02/msg00294.html
I replaced that `sleep-for' with a call to the 'sleep' binary...
- Connecting to Gmane seems to be unreliable, so I disabled running the
test for now.
-David
next prev parent reply other threads:[~2015-05-31 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Yy7fd-0004tU-Ps@randomsample.de>
2015-05-29 0:13 ` [Buildbot] Gnus build failed Katsumi Yamaoka
2015-05-31 10:44 ` David Engster [this message]
2015-05-31 22:45 ` Katsumi Yamaoka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpzpni0u.fsf@isaac.fritz.box \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).