From: Jim Porter <jporterbugs@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 65602@debbugs.gnu.org
Subject: bug#65602: 30.0.50; eshell-test/{elisp,subcommand}-reset-in-pipeline fails intermittently on macOS
Date: Wed, 13 Sep 2023 18:24:17 -0700 [thread overview]
Message-ID: <3c4abdbc-43de-6adb-2c78-fc937ff0f472@gmail.com> (raw)
In-Reply-To: <CADwFkmkTADCFLHKibp2z7OWhL2t2tREKKjfOeBgymEFeVrSVnQ@mail.gmail.com>
On 9/13/2023 2:33 PM, Stefan Kangas wrote:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> I spoke too soon, as I'm now seeing the below two failures.
>>
>> FAILED 42/110 esh-var-test/interp-var-indices-subcommand (0.787189 sec) at lisp/eshell/esh-var-tests.el:184
>>
>> FAILED 5/11 eshell-test/eshell-command/simple (0.670351 sec) at lisp/eshell/eshell-tests.el:41
>
> Here's another one I saw in another rerun:
>
> FAILED esh-var-test/interp-concat-cmd-external
Hmm. I pushed a commit to add additional instrumentation to this code
(ef2bd5e4875). Could you try that out and report the results?
You could also try adding something like "(setq eshell-debug-command
'(form))" to the top of "test/lisp/eshell/eshell-tests-helpers.el", and
then "rm test/lisp/eshell/*.elc" to force a full recompile of the tests.
That'll add excessive amounts of logging for Eshell's s-expr
manipulation, and it might produce something useful. (Warning that it
can also include things like your env vars in the logs, so be careful
about uploading it.)
next prev parent reply other threads:[~2023-09-14 1:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:44 bug#65590: 29.0.50; esh-var-test/interp-concat-cmd fails on macOS Stefan Kangas
2023-08-29 17:10 ` Jim Porter
2023-08-29 18:59 ` Stefan Kangas
2023-08-29 19:15 ` Stefan Kangas
2023-08-30 0:44 ` Jim Porter
2023-09-01 1:54 ` Jim Porter
2023-09-01 16:03 ` Stefan Kangas
2023-09-01 16:30 ` Jim Porter
2023-09-01 17:00 ` Jim Porter
2023-09-12 18:53 ` Jim Porter
2023-09-13 16:10 ` Stefan Kangas
2023-09-13 18:54 ` Jim Porter
2023-09-13 20:34 ` Stefan Kangas
2023-09-13 20:41 ` Jim Porter
2023-09-13 20:48 ` Stefan Kangas
2023-09-13 21:10 ` bug#65590: bug#65602: 30.0.50; eshell-test/{elisp,subcommand}-reset-in-pipeline fails intermittently " Stefan Kangas
2023-09-13 21:33 ` Stefan Kangas
2023-09-14 1:24 ` Jim Porter [this message]
2023-09-14 19:14 ` Stefan Kangas
2023-09-14 19:33 ` Jim Porter
2023-09-15 0:59 ` Jim Porter
2023-09-15 12:14 ` Stefan Kangas
2023-09-18 17:30 ` Jim Porter
2023-09-13 21:13 ` bug#65590: " Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 19:37 Stefan Kangas
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=3c4abdbc-43de-6adb-2c78-fc937ff0f472@gmail.com \
--to=jporterbugs@gmail.com \
--cc=65602@debbugs.gnu.org \
--cc=stefankangas@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.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).