From: Alan Third <alan@idiocy.org>
To: John Wiegley <johnw@gnu.org>
Cc: 29712@debbugs.gnu.org
Subject: bug#29712: 26.0.90; Three emacs-26 elisp tests are failing on darwin
Date: Wed, 10 Jan 2018 00:12:19 +0000 [thread overview]
Message-ID: <20180110001219.GA46158@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2efn0uk42.fsf@newartisans.com>
On Mon, Jan 08, 2018 at 01:16:29PM -0800, John Wiegley wrote:
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>
> EZ> Yes, for the release branch only.
>
> I'm still seeing one failure with the current emacs-26:
>
> --8<---------------cut here---------------start------------->8---
> ELC lisp/eshell/em-ls-tests.elc
I can’t replicate this failure at all:
Running 4 tests (2018-01-09 23:55:30+0000)
passed 1/4 em-ls-test-bug27631
passed 2/4 em-ls-test-bug27817
passed 3/4 em-ls-test-bug27843
passed 4/4 em-ls-test-bug27844
Ran 4 tests, 4 results as expected (2018-01-09 23:55:30+0000)
Does
(dired (expand-file-name "lisp/subr.el" source-directory))
work?
--
Alan Third
next prev parent reply other threads:[~2018-01-10 0:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 16:46 bug#29712: 26.0.90; Three emacs-26 elisp tests are failing on darwin John Wiegley
2017-12-15 8:39 ` Michael Albinus
2017-12-16 1:02 ` Alan Third
2017-12-16 10:23 ` Michael Albinus
2017-12-16 13:47 ` Alan Third
2017-12-16 15:55 ` Michael Albinus
2017-12-16 1:10 ` Alan Third
2017-12-16 8:34 ` Eli Zaretskii
2017-12-16 9:46 ` Alan Third
2017-12-16 10:35 ` Eli Zaretskii
2017-12-16 13:42 ` Alan Third
2017-12-16 14:15 ` Eli Zaretskii
2017-12-16 15:07 ` Alan Third
2017-12-16 16:19 ` Eli Zaretskii
2017-12-16 16:42 ` Alan Third
2017-12-16 16:47 ` Eli Zaretskii
2017-12-16 17:01 ` Alan Third
2017-12-16 17:19 ` Eli Zaretskii
2018-01-08 21:16 ` John Wiegley
2018-01-10 0:12 ` Alan Third [this message]
2018-01-29 18:43 ` John Wiegley
2018-01-30 21:44 ` Alan Third
2018-01-30 22:40 ` John Wiegley
2018-01-31 20:03 ` Alan Third
2018-02-01 18:05 ` Glenn Morris
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=20180110001219.GA46158@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=29712@debbugs.gnu.org \
--cc=johnw@gnu.org \
/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.