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: Thu, 14 Sep 2023 17:59:16 -0700 [thread overview]
Message-ID: <398f97d8-fc1c-2a96-ab70-ef74002e1b82@gmail.com> (raw)
In-Reply-To: <b44ddc72-930d-ee33-2508-a9cd415fc708@gmail.com>
On 9/14/2023 12:33 PM, Jim Porter wrote:
> On 9/14/2023 12:14 PM, Stefan Kangas wrote:
>> I have sent the logs to you off-list.
>
> Thanks for the logs. They're pretty large, so I'll have to take some
> extra time to look them over, but I'm beginning to wonder if there's a
> bug in process.c. In the logs for em-unix-tests, I see messages for the
> start of the "echo" process and its sentinel, but nothing for the output
> filter, even though we *should* be getting output. I'll keep thinking
> about this, and possibly add some further instrumentation to narrow this
> down...
I pushed some minor changes to the logging (cadd3326625), and a
mostly-unrelated fix to Eshell's iterative evaluation that I noticed
from perusing the logs (one day I should really just rip that out and
replace it with generator.el...).
In particular, I added logging for the actual command-line args that we
pass to external commands. That should help to narrow down whether we're
calling the subprocess correctly, or if there's some issue where the
expected output gets lost on the way somewhere...
next prev parent reply other threads:[~2023-09-15 0:59 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
2023-09-14 19:14 ` Stefan Kangas
2023-09-14 19:33 ` Jim Porter
2023-09-15 0:59 ` Jim Porter [this message]
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=398f97d8-fc1c-2a96-ab70-ef74002e1b82@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).