From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master updated (5af5ed6c62 -> f07505d1ec)
Date: Sun, 4 Sep 2022 17:25:23 -0700 [thread overview]
Message-ID: <fd3bec63-0a09-a2be-2f1d-fe391b32a960@gmail.com> (raw)
In-Reply-To: <87fsh665fj.fsf@gnus.org>
On 9/4/2022 5:17 PM, Lars Ingebrigtsen wrote:
> After this patch series, I'm getting:
>
> 4 unexpected results:
> FAILED esh-proc-test/exit-status/with-stderr-pipe
> FAILED esh-proc-test/output/stderr-to-buffer
> FAILED esh-proc-test/output/stdout-and-stderr-to-buffer
> FAILED esh-proc-test/output/stdout-to-buffer
>
> This is on Debian/bookworm.
If the errors say anything about 'eshell-with-temp-buffer', you might
just need to run "rm test/lisp/eshell/*.elc" to force a full recompile
of the Eshell test suite.
Several of the tests use a common eshell-tests-helpers.el file, which I
updated with a new macro (the aforementioned 'eshell-with-temp-buffer').
Unfortunately, the tests aren't smart enough to recompile
eshell-tests-helpers.el first in cases like this. If anyone knows of a
good way to do this, a patch (or even just a pointer in the right
direction) would be great.
I probably should have sent a warning about this to emacs-devel, but I
forgot that I touched eshell-tests-helpers.el in that patch series.
next prev parent reply other threads:[~2022-09-05 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166233264971.21612.17042094685015365861@vcs2.savannah.gnu.org>
2022-09-05 0:17 ` master updated (5af5ed6c62 -> f07505d1ec) Lars Ingebrigtsen
2022-09-05 0:18 ` Lars Ingebrigtsen
2022-09-05 0:22 ` Lars Ingebrigtsen
2022-09-05 0:25 ` Jim Porter [this message]
2022-09-06 9:33 ` Lars Ingebrigtsen
2022-09-06 18:41 ` Jim Porter
2022-09-06 20:13 ` Lars Ingebrigtsen
2022-09-06 22:46 ` Jim Porter
2022-09-07 11:46 ` Lars Ingebrigtsen
2022-09-07 21:03 ` Jim Porter
2022-09-08 12:02 ` Lars Ingebrigtsen
2022-09-08 22:16 ` Jim Porter
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd3bec63-0a09-a2be-2f1d-fe391b32a960@gmail.com \
--to=jporterbugs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).