Re: Test failure with current head

[Rasmus <rasmus@gmx.us>]

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