From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: Failed: Hydra job gnu:emacs-trunk:coverage on x86_64-linux
Date: Fri, 02 Jun 2017 13:32:42 +0200 [thread overview]
Message-ID: <87lgpapqud.fsf@rosalinde> (raw)
In-Reply-To: <87poempyyx.fsf@rosalinde> (Stephen Berman's message of "Fri, 02 Jun 2017 10:37:10 +0200")
On Fri, 02 Jun 2017 10:37:10 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
> On Fri, 2 Jun 2017 08:53:08 +0200 Hydra Build Daemon
> <edolstra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> The status of Hydra job ‘gnu:emacs-trunk:coverage’ (on x86_64-linux) has
>> changed from "Success" to "Failed". For details, see
>>
>> https://hydra.nixos.org/build/53544385
>>
>> This may be due to a commit by Stephen Berman
>> <stephen.berman-hi6Y0CQ0nG0@public.gmane.org>.
>
> The Hydra log shows this:
>
> lisp/calendar/todo-mode-tests.log:
> FAILED todo-test-item-highlighting
>
> But I just ran make check on my master branch, which contains exactly
> the test file I patched in 8c0f845, and all tests passed:
>
> Running 3 tests (2017-06-02 10:20:32+0200)
> passed 1/3 todo-test-item-highlighting
> passed 2/3 todo-test-todo-quit01
> passed 3/3 todo-test-todo-quit02
>
> Ran 3 tests, 3 results as expected (2017-06-02 10:20:32+0200)
>
> (I even renamed my local todo directory before running the tests, though
> with the patch that shouldn't matter.) So I have no idea why the test
> failed on Hydra.
I overlooked the commit hash (and the build date) of the Hydra report:
that was after my initial commit of the tests, which was indeed faulty.
Sorry for the false alarm.
Steve Berman
prev parent reply other threads:[~2017-06-02 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170602065308.926C61C153F@hydra.nixos.org>
2017-06-02 8:37 ` Failed: Hydra job gnu:emacs-trunk:coverage on x86_64-linux Stephen Berman
2017-06-02 11:32 ` Stephen Berman [this message]
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=87lgpapqud.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@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 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).