unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Ulf Jasper <ulf.jasper@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: icalendar-real-world test sometimes fails
Date: Thu, 24 Jul 2014 16:17:20 -0400	[thread overview]
Message-ID: <b18unih5pr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87fvhq7k6m.fsf@web.de> (Ulf Jasper's message of "Thu, 24 Jul 2014 19:14:57 +0200")

Ulf Jasper wrote:

> I'm wondering why the test fails "sometimes".  Does that really mean
> that the test finishes successfully one day but fails the next day?

Yes! :)
It (randomly?) pings back and forth between success and failure for no
reason I can fathom.

http://hydra.nixos.org/build/12698548    # works, trunk r117565
http://hydra.nixos.org/build/12699658    # fails, trunk r117566
http://hydra.nixos.org/build/12711693    # works, trunk r117567

It has been doing this for a while, in emacs-24 branch too.
It usually works, but once in a while it fails.

> In any case I would prefer to fix the root cause instead of modifying
> the test case.  The "# coding..."  should not get inserted into the
> diary file, should it?  Where does it come from?

That's the question...



  reply	other threads:[~2014-07-24 20:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 20:48 icalendar-real-world test sometimes fails Glenn Morris
2014-07-24 17:14 ` Ulf Jasper
2014-07-24 20:17   ` Glenn Morris [this message]
2014-07-26 13:00     ` Ulf Jasper
2014-07-27 20:30       ` Glenn Morris
2014-07-28 16:27         ` Ulf Jasper
2014-07-28 22:56           ` Glenn Morris
2014-07-29 16:34             ` Ulf Jasper
2014-07-29 23:57               ` Glenn Morris
2014-07-30 17:16                 ` Ulf Jasper
2014-07-30 23:18                   ` Glenn Morris
2014-07-31 17:05                     ` Ulf Jasper
2014-08-02  5:47                       ` Glenn Morris
2014-08-02 13:39                         ` Ulf Jasper
2014-08-03 20:25                           ` Glenn Morris
2014-08-04 17:56                             ` Ulf Jasper

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=b18unih5pr.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ulf.jasper@web.de \
    /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).