From: John Hendy <jw.hendy@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Heads-up: test failures
Date: Tue, 14 Feb 2017 20:32:59 -0600 [thread overview]
Message-ID: <CA+M2ft--b=Qk=bqtWc8QmGA7DPxh-pNYQUP71B2+=Dhk5fdSKA@mail.gmail.com> (raw)
In-Reply-To: <87d1emexl3.fsf@alphaville.usersys.redhat.com>
On Mon, Feb 13, 2017 at 12:48 PM, Nick Dokos <ndokos@gmail.com> wrote:
> 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:
Since others are adding in to the party! I ran after a fresh pull on
my normal setup.
$ uname -a
Linux whammy 4.9.8-1-ARCH #1 SMP PREEMPT Mon Feb 6 12:59:40 CET 2017
x86_64 GNU/Linux
$ emacs --version
GNU Emacs 25.1.1
M-x org-version
Org mode version 9.0.5 (release_9.0.5-288-g4caad0 @
/home/jwhendy/.elisp/org/lisp/)
Ran 705 tests, 705 results as expected (2017-02-14 20:12:26-0600)
9 expected failures
Since there was some mention of the emacs version, I just grabbed the
Arch AUR emacs-git package and re-ran. This is with 26.0.50.1:
Ran 705 tests, 701 results as expected, 4 unexpected (2017-02-14 20:28:42-0600)
9 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
Looks like emacs version is involved.
John
>
> --
> Nick
>
>
>
next prev parent reply other threads:[~2017-02-15 2:33 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
2017-02-14 22:26 ` Nick Dokos
2017-02-15 5:53 ` Colin Baxter
2017-02-15 2:32 ` John Hendy [this message]
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='CA+M2ft--b=Qk=bqtWc8QmGA7DPxh-pNYQUP71B2+=Dhk5fdSKA@mail.gmail.com' \
--to=jw.hendy@gmail.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 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.