From: Ulf Jasper <ulf.jasper@web.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: icalendar-real-world test sometimes fails
Date: Thu, 31 Jul 2014 19:05:23 +0200 [thread overview]
Message-ID: <87r411e9ws.fsf@web.de> (raw)
In-Reply-To: <1ja97q306d.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 30 Jul 2014 19:18:50 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Ulf Jasper wrote:
>
>> If I understand test/automated/Makefile correctly then log files are
>> written for each test. Are they kept when the hydra job is finished?
>
> I don't think so, though it may be possible for me to make it so they
> are.
That would be very helpful.
> Anyway, we just had another failure, this time in
> icalendar--decode-isodatetime:
>
> http://hydra.nixos.org/build/12974200/log/raw
>
> It's probably some quirk of the system, but it would be good to suppress
> such failures if possible.
That is the new test `icalendar--decode-isodatetime' which I added just
yesterday. Before committing I have checked it on two different
systems.
Luckily I forgot to remove the lines
(message "%s" (current-time-zone (encode-time 0 0 10 1 1 2013 0)))
(message "%s" (current-time-zone (encode-time 0 0 10 1 8 2013 0)))
from the test. They should result in the ouput
(3600 EET)
(7200 EET)
but the log file shows
(0 EET)
(0 EET)
It looks as if hydra does not know the time zone "EET". That is strange.
next prev parent reply other threads:[~2014-07-31 17:05 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r411e9ws.fsf@web.de \
--to=ulf.jasper@web.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.