From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Test failure with current head
Date: Wed, 15 Jul 2015 22:40:20 +0200 [thread overview]
Message-ID: <87k2u1yx1n.fsf@gmx.us> (raw)
In-Reply-To: 87twt5i2ix.fsf@isaac.fritz.box
David Engster <deng@randomsample.de> writes:
> Nick Dokos writes:
>> Rasmus <rasmus@gmx.us> writes:
>>
>
>>> Nick Dokos <ndokos@gmail.com> writes:
>>>
>>>> I just updated to release_8.3beta-1286-g20795fd.
>>>>
>>>> ``make test'' shows a failure on test 226:
>>>> FAILED 226/592 test-org-clock/clocktable-until-now
>>>>
>>>>
>>>> The backtrace was edited to get rid of a NUL that gnus complained
>>>
>>> I know. I don't really understand what untilnow does and the org
>>> clocktable tests are really obscure to me. Fell free to do a bisect
>>> master or/and submit a fix.
>>>
>>
>> Seems like a heisenbug - first attempt to bisect fingered
>> 20795fd1c4e48096226f3072de8d93bd99d761bf but only because it is the HEAD
>> and I had declared it as bad: it turns out that `make test' does not
>> get any failures now. And nothing changed - weird.
>
> Yes, it's not always failing, but it's been happening for a few days now
> on the buildbot:
>
> http://randomsample.de/org-buildbot
>
> First time it happened was after this commit
>
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=22c652599c8bfedcd27e78d7ad9544826eae7dd0
>
> but it looks harmless. Could very well be something else that triggers
> this.
This is in contrib. AFAIK it is not covered by make test.
--
This is the kind of tedious nonsense up with which I will not put
next prev parent reply other threads:[~2015-07-15 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:36 Test failure with current head Nick Dokos
2015-07-15 16:45 ` Rasmus
2015-07-15 20:10 ` Nick Dokos
2015-07-15 20:33 ` David Engster
2015-07-15 20:40 ` Rasmus [this message]
2015-07-15 20:37 ` Rasmus
2015-07-16 3:35 ` Nick Dokos
2015-07-16 8:34 ` Rasmus
2015-07-16 13:10 ` Nick Dokos
2015-07-17 22:45 ` Nicolas Goaziou
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=87k2u1yx1n.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@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.