unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Building master hangs generating lisp/eshell/esh-util-tests.log
Date: Thu, 13 Jun 2024 10:43:16 +0000	[thread overview]
Message-ID: <ZmrNRBOGEYESmURy@ACM> (raw)
In-Reply-To: <yp1o785jl3f.fsf@fencepost.gnu.org>

Hello, Andrea.

On Thu, Jun 13, 2024 at 04:36:04 -0400, Andrea Corallo wrote:
> Eli Zaretskii <eliz@gnu.org> writes:

> >> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> >> Date: Wed, 12 Jun 2024 17:54:38 +0200

> >> I have retried to build master and the process hangs at
> >> GEN      lisp/eshell/esh-util-tests.log

> > I don't understand.  First, a build doesn't include running the test
> > suite, so what do you mean by "the build process hangs at"?

> > And second, running this:

> >   $ make -C test lisp/eshell/esh-util-tests

> > doesn't hang here.  This is with the current master branch.

> I see hangs during tests on my local CI as well since about 2 3 days,
> but unfortunatelly they are not very reproducible.  I'll try to gain
> some more data points.

I've just updated my master repo.  It built OK, and on running make
check, two erc test files hung.  After killing them (after ~2 minutes run
time), I got the following display on my terminal:

SUMMARY OF TEST RESULTS
-----------------------
Files examined: 518
Ran 7858 tests, 28 failed to run, 7659 results as expected, 1 unexpected,
198 skipped
2 files did not finish:
  lisp/eshell/esh-proc-tests.log
  lisp/eshell/esh-ext-tests.log
1 files contained unexpected results:
  lisp/minibuffer-tests.log

I got basically the same on running make check in one of my other repos
which I'd just updated.  So the problem appears to be reproducible for
me.

>   Andrea

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2024-06-13 10:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 15:54 Building master hangs generating lisp/eshell/esh-util-tests.log Pedro Andres Aranda Gutierrez
2024-06-12 17:02 ` Eli Zaretskii
2024-06-12 17:43   ` Stefan Kangas
2024-06-13  8:36   ` Andrea Corallo
2024-06-13 10:43     ` Alan Mackenzie [this message]
2024-06-13 13:14       ` Andrea Corallo
2024-06-13 16:20         ` Steven Allen
2024-06-13 20:30         ` Dmitry Gutov
2024-06-13 22:55           ` Andrea Corallo
2024-06-13 23:44             ` Dmitry Gutov
2024-06-14  5:09           ` Pedro Andres Aranda Gutierrez
2024-06-12 19:09 ` Jim Porter
2024-06-13  6:14   ` Pedro Andres Aranda Gutierrez
2024-06-13 19:19     ` Jim Porter
2024-06-13 20:29       ` Dmitry Gutov
2024-06-13 20:35         ` Jim Porter
2024-06-13 20:48           ` Dmitry Gutov

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=ZmrNRBOGEYESmURy@ACM \
    --to=acm@muc.de \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@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).