emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Heads-up: test failures
Date: Tue, 14 Feb 2017 21:28:08 +0000	[thread overview]
Message-ID: <8737fgqx7b.fsf@yandex.com> (raw)
In-Reply-To: <87r330elih.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Tue, 14 Feb 2017 12:21:26 -0500")

On Tue, Feb 14 2017, Nick Dokos wrote:

> Colin Baxter <m43cap@yandex.com> writes:
>
>> On Mon, Feb 13 2017, Nick Dokos wrote:
>>
>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>>
>>>> What is the failure in each case?
>>>
>> ---- snip ----
>>
>> Ran 711 tests, 711 results as expected (2017-02-14 07:58:32+0000)
>> 8 expected failures
>>
>> org-mode release_9.0.5-282-g2e32709
>> emacs-25.1.1; 3.2.0-4-686-pae #1 SMP Debian 3.2.84-1 i686 GNU/Linux
>>
>>
>
> It might be that emacs 26 shows the failures (both Marco Wahl and I are
> running that, but Colin Baxter runs emacs 25 and does not see them).


Unfortunately, the tests pass using emacs-26 too:

Ran 711 tests, 711 results as expected (2017-02-14 21:21:38+0000)
8 expected failures

org-version: 9.0.5 (release_9.0.5-288-g4caad0)
GNU Emacs 26.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2) of 2017-02-11


Best wishes,

Colin.

  reply	other threads:[~2017-02-14 21:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 18:48 Heads-up: test failures Nick Dokos
2017-02-13 19:36 ` Marco Wahl
2017-02-13 20:34   ` Nicolas Goaziou
2017-02-13 21:11     ` Nick Dokos
2017-02-14  8:08       ` Colin Baxter
2017-02-14 17:21         ` Nick Dokos
2017-02-14 21:28           ` Colin Baxter [this message]
2017-02-14 22:26             ` Nick Dokos
2017-02-15  5:53               ` Colin Baxter
2017-02-15  2:32 ` John Hendy
2017-02-15  3:53   ` Vladimir Lomov

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=8737fgqx7b.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --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
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/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).