From: Philipp Stephani <p.stephani2@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs | Pipeline #8399 has failed for master | ee0e259e
Date: Tue, 5 Jan 2021 14:44:56 +0100 [thread overview]
Message-ID: <CAArVCkTqtb1oP3W75Esh4SJzOoggczvnFXWs1EwRDkQkd6ajTQ@mail.gmail.com> (raw)
In-Reply-To: <87im8b3jo6.fsf@gmx.de>
Am Di., 5. Jan. 2021 um 08:52 Uhr schrieb Michael Albinus
<michael.albinus@gmx.de>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> >> process-test-sentinel-wait-function-working-p which is used by
> >> process-test-sentinel-sit-for looks racy. Just because the process
> >> sentinel has been called is no guarantee that the process has exited
> >> and had its process-status set correctly, perhaps it should loop on
> >> 'process-live-p'
> >
> > AFAIK the only correct way to wait for a process to exit is (while
> > (accept-process-output PROC)).
>
> I vaguely remember that Stefan did propose (while (accept-process-output
> PROC 0)).
I guess that would work as well, but wouldn't it result in a busy
wait? OTOH, accept-process-output with an infinite timeout should
return immediately if the process has terminated (i.e. Emacs has
processed the SIGCHLD signal).
next prev parent reply other threads:[~2021-01-05 13:44 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 [this message]
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
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=CAArVCkTqtb1oP3W75Esh4SJzOoggczvnFXWs1EwRDkQkd6ajTQ@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).