unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	 emacs-build-automation@gnu.org, emacs-devel@gnu.org
Subject: Re: broken "fast" build - hung containers
Date: Sat, 18 Sep 2021 20:01:36 +0000	[thread overview]
Message-ID: <fsu1mz4v.fsf@lifelogs.com> (raw)
In-Reply-To: <87mtocmr6h.fsf@gmx.de> (Michael Albinus's message of "Thu, 16 Sep 2021 18:16:38 +0200")

I was able to replicate the bug by going into one of the hung containers
and running `make check`. It hangs in the module tests, and ends with a
kernel fault (this is 4.4.0). It seems that the
`module--help-function-arglist` test is the last one to succeed, and
`module--test-assertions--load-non-live-object` is the next one that may
be the failing one.

```
# docker exec -it [hung-container-ID] bash
# make -C lib all
make[1]: Entering directory '/checkout/lib'
...
GEN      src/editfns-tests.log
GEN      src/emacs-module-tests.log
2021 Sep 18 06:39:13 emba kernel BUG at /build/linux-Pv5wqf/linux-4.4.0/mm/memory.c:3214!
2021 Sep 18 06:39:13 emba RIP  [<ffffffff811cd1ae>] handle_mm_fault+0x13de/0x1b80

^C

Makefile:181: recipe for target 'src/emacs-module-tests.log' failed
make[3]: *** [src/emacs-module-tests.log] Interrupt
Makefile:335: recipe for target 'check-doit' failed
make[2]: [check-doit] Interrupt (ignored)
Makefile:305: recipe for target 'check' failed
make[1]: *** [check] Interrupt
Makefile:988: recipe for target 'check' failed
make: *** [check] Interrupt
```

So. I removed emacs-module-tests.* and the test kept going until
process-tests.* where it locked up with the same kernel bug.

I removed process-tests.* as well, and all the tests completed.

Could we disable the emacs-module-tests.el and process-tests.el inside
EMBA Docker?

For the EMBA admins: this can be replicated with

docker exec -it $(docker ps -q|shuf|head -1) bash

and then `make check` (which will randomly pick one of the dozens of
hung containers). I can dig further if someone can give me steps to
follow.

Thanks
Ted



  reply	other threads:[~2021-09-18 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a6kepd77.fsf@lifelogs.com>
2021-09-15  8:09 ` broken "fast" build - hung containers Lars Ingebrigtsen
2021-09-15  9:57 ` emba.el (was: broken "fast" build - hung containers) Michael Albinus
2021-09-16  8:31   ` emba.el Ted Zlatanov
2021-09-16 16:26     ` emba.el Michael Albinus
     [not found] ` <87fsu6p4bx.fsf@gmx.de>
2021-09-16 12:44   ` broken "fast" build - hung containers Ted Zlatanov
2021-09-16 16:16     ` Michael Albinus
2021-09-18 20:01       ` Ted Zlatanov [this message]
2021-09-18 21:13         ` Michael Albinus
2021-09-19  8:25           ` Ted Zlatanov
2021-09-19 14:49             ` Lars Ingebrigtsen
2021-09-20 11:53             ` Michael Albinus

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=fsu1mz4v.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-build-automation@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).