unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Po Lu <luangruo@yahoo.com>, Glenn Morris <rgm@gnu.org>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	Philipp Stephani <phst@google.com>,
	56424@debbugs.gnu.org
Subject: bug#56424: hydra.nixos coverage job times out
Date: Tue, 19 Jul 2022 14:52:34 +0200	[thread overview]
Message-ID: <CAArVCkTffS401SGbTZh-w736OKsbQ4O7nu3+iUE=TF0fjJB66Q@mail.gmail.com> (raw)
In-Reply-To: <87pmidb0r2.fsf@gmx.de>

Am So., 10. Juli 2022 um 14:40 Uhr schrieb Michael Albinus
<michael.albinus@gmx.de>:
>
> Glenn Morris <rgm@gnu.org> writes:
>
> Hi Glenn,
>
> > With increased logging, and a serial build, we can see that it times out
> > in process-tests:
> > https://hydra.nixos.org/build/183466954
>
> The incrimed test is process-tests/fd-setsize-no-crash/make-process.
> From EMBA, I know that there are sometimes problems with this test
> package, that's why we have suppressed
> process-tests/multiple-threads-waiting on EMBA, for example. Maybe
> something similar shall be done for HYDRA?
>
> I've CC'ed Philipp Stephani, the author of this test package, for
> further analysis.


My 2 cents: These timeouts/failures indicate real bugs in Emacs. They
are incredibly hard to debug due to the enormous complexity in Emacs's
asynchronous process handling code, but just skipping them won't make
the bugs go away. Somebody should at least try to dig into these
issues. But probably that requires something like the CI system
creating a snapshot of the failed tests as a Docker container that one
could SSH into, because the failures tend to be impossible to
reproduce locally.





  reply	other threads:[~2022-07-19 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 17:47 bug#56424: hydra.nixos coverage job times out Glenn Morris
2022-07-07  9:04 ` Lars Ingebrigtsen
2022-07-07 10:07   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-07 17:34     ` Lars Ingebrigtsen
2022-07-10 10:44       ` Michael Albinus
2022-07-10 20:09         ` Michael Albinus
2022-07-10  2:02   ` Glenn Morris
2022-07-10 12:39     ` Michael Albinus
2022-07-19 12:52       ` Philipp Stephani [this message]
2022-07-10 13:00     ` Lars Ingebrigtsen
2022-10-11  1:03 ` Lars Ingebrigtsen

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='CAArVCkTffS401SGbTZh-w736OKsbQ4O7nu3+iUE=TF0fjJB66Q@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=56424@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=michael.albinus@gmx.de \
    --cc=phst@google.com \
    --cc=rgm@gnu.org \
    /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).