From: Robert Pluim <rpluim@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs | Pipeline #8399 has failed for master | ee0e259e
Date: Tue, 05 Jan 2021 10:42:53 +0100 [thread overview]
Message-ID: <874kjv3ejm.fsf@gmail.com> (raw)
In-Reply-To: <CAArVCkSKVrCyU3zEDVHazQxLhaPuj3hrzUKLfX1Djuiw1SnG7w@mail.gmail.com> (Philipp Stephani's message of "Mon, 4 Jan 2021 21:38:07 +0100")
Philipp Stephani <p.stephani2@gmail.com> writes:
>> The process-test-stderr-buffer timeout I can't explain: nothing there
>> can wait longer than 2 seconds (unless itʼs 'make-process' thatʼs
>> timing out?)
>
> make-process can in theory deadlock on BSD-like systems due to a race
> between setting the close-on-exec flag and other fork+exec
> combinations. That's rather unlikely though.
> But maybe there's a race between accept-process-output and calling the
> sentinel so that the sentinel is called too early, and then
> accept-process-output blocks? AFAIK, when splitting stderr and stdout,
> one has to wait separately for the two involved processes:
> (while (accept-process-output process))
> (while (accept-process-output stderr-process))
The code is this:
(while (not (or sentinel-called
(> (- (float-time) start-time)
process-test-sentinel-wait-timeout)))
(accept-process-output))
You mean between checking 'sentinel-called' and
'accept-process-output', the sentinel is called, the process exit's and
then 'accept-process-output' hangs? I guess thatʼs possible. We could
add a timeout to accept-process-output to verify.
To your other point: thereʼs only one process involved here, stderr is
being sent to a separate buffer (although using a separate process is
possible as well).
Robert
next prev parent reply other threads:[~2021-01-05 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5feaf98365b55_3f903d428113941@emba.gnu.org.mail>
2020-12-29 15:50 ` emacs | Pipeline #8399 has failed for master | ee0e259e Michael Albinus
2020-12-29 17:12 ` Robert Pluim
2020-12-29 17:42 ` Michael Albinus
2020-12-29 21:23 ` Michael Albinus
2021-01-04 17:20 ` Robert Pluim
2021-01-04 20:38 ` Philipp Stephani
2021-01-05 7:52 ` Michael Albinus
2021-01-05 13:44 ` Philipp Stephani
2021-01-06 12:15 ` Michael Albinus
2021-01-17 10:37 ` Philipp Stephani
2021-01-17 12:42 ` Michael Albinus
2021-01-17 13:21 ` Philipp Stephani
2021-01-05 9:42 ` Robert Pluim [this message]
2021-01-05 9:55 ` Andreas Schwab
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=874kjv3ejm.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=p.stephani2@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).