From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Heads-up: test failures
Date: Mon, 13 Feb 2017 21:34:00 +0100 [thread overview]
Message-ID: <87d1elltjb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <84tw7xj32y.fsf@tm6592> (Marco Wahl's message of "Mon, 13 Feb 2017 20:36:05 +0100")
Hello,
Marco Wahl <marcowahlsoft@gmail.com> writes:
> Nick Dokos <ndokos@gmail.com> writes:
>
>> I just updated to
>>
>> Org mode version 9.0.5 (release_9.0.5-260-geb59c7 @ /home/nick/elisp/org-mode/lisp/)
>>
>> and `make test' gives me:
>>
>> ,----
>> | Ran 710 tests, 706 results as expected, 4 unexpected (2017-02-13 13:41:50-0500)
>> | 7 expected failures
>> |
>> | 4 unexpected results:
>> | FAILED test-org-list/move-item-down
>> | FAILED test-org-list/move-item-up
>> | FAILED test-org/custom-properties
>> | FAILED test-org/forward-paragraph
>> `----
>
> I see these line also. I thought this was something crazy with my
> individual settings.
>
> #+begin_example
> Ran 704 tests, 700 results as expected, 4 unexpected (2017-02-13 20:32:03+0100)
> 8 expected failures
>
> 4 unexpected results:
> FAILED test-org-list/move-item-down
> FAILED test-org-list/move-item-up
> FAILED test-org/custom-properties
> FAILED test-org/forward-paragraph
> #+end_example
What is the failure in each case?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-02-13 20:34 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1elltjb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=marcowahlsoft@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 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.