emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: David Engster <deng@randomsample.de>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Test failure with current head
Date: Wed, 15 Jul 2015 22:33:58 +0200	[thread overview]
Message-ID: <87twt5i2ix.fsf@isaac.fritz.box> (raw)
In-Reply-To: <874ml5uqqq.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Wed, 15 Jul 2015 16:10:05 -0400")

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.

-David

next prev parent reply	other threads:[~2015-07-15 20:34 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 [this message]
2015-07-15 20:40       ` Rasmus
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twt5i2ix.fsf@isaac.fritz.box \
    --to=deng@randomsample.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).