From: Robert Pluim <rpluim@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: emacs | Pipeline #8399 has failed for master | ee0e259e
Date: Mon, 04 Jan 2021 18:20:31 +0100 [thread overview]
Message-ID: <87h7nw39gg.fsf@gmail.com> (raw)
In-Reply-To: <8735zo9ui7.fsf@gmx.de> (Michael Albinus's message of "Tue, 29 Dec 2020 22:23:28 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Hi Robert,
>
>>> Is there a way to get src/process-tests.log? That would at least
>>> narrow it down.
>>
>> No, the whole CI job runs into a timeout. I have wrapped now all tests
>> in process-tests.el with a timeout of 60 seconds; hopefully it shows us
>> the log file in case of.
>
> See <https://emba.gnu.org/emacs/emacs/-/jobs/9636/raw>.
> process-test-sentinel-sit-for has produced a failure. And according to
> the timestamps, process-test-stderr-buffer ran into the timeout.
>
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'
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?)
Robert
next prev parent reply other threads:[~2021-01-04 17:20 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 [this message]
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
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=87h7nw39gg.fsf@gmail.com \
--to=rpluim@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).