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: Philipp Stephani <phst@google.com>, 50902@debbugs.gnu.org
Subject: bug#50902: 28.0.50; emacs-module-tests time out
Date: Sun, 31 Oct 2021 19:10:07 +0100	[thread overview]
Message-ID: <CAArVCkSRtzEDRnLK9FvKN02WEXNYfsE-DT7cK2ZvMhF-PvjwBg@mail.gmail.com> (raw)
In-Reply-To: <87czntdzyu.fsf@gmx.de>

Am Mo., 25. Okt. 2021 um 14:57 Uhr schrieb Michael Albinus
<michael.albinus@gmx.de>:
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> Hi Philipp,
>
> > Both outputs don't look too informative. What else can I do? Do you want
> > to get the core files? Note, that I'm not fluent with gdb; precise
> > instructions are needed.
>
> I've tried now to run the test interactively, after log in to the docker
> container:
>
> --8<---------------cut here---------------start------------->8---
> root@2499288dd2cf:/checkout# make -C test emacs-module-tests
> make: Entering directory '/checkout/test'
> make[1]: Entering directory '/checkout/test'
>   GEN      src/emacs-module-tests.log
> Running 38 tests (2021-10-25 12:52:58+0000, selector `(not (or (tag :unstable) (tag :nativecomp)))')
>    passed   1/38  emacs-module-tests/interleaved-threads (0.006767 sec)
>    passed   2/38  mod-test-add-nanosecond/invalid (0.000289 sec)
>    passed   3/38  mod-test-add-nanosecond/nil (0.000123 sec)
>    passed   4/38  mod-test-add-nanosecond/valid (0.000579 sec)
>    passed   5/38  mod-test-double (0.000302 sec)
>    passed   6/38  mod-test-globref-free-test (0.000150 sec)
>    passed   7/38  mod-test-globref-make-test (0.055301 sec)
>    passed   8/38  mod-test-globref-reordered (0.000733 sec)
>    passed   9/38  mod-test-make-string/empty (0.000503 sec)
>    passed  10/38  mod-test-make-string/nonempty (0.000600 sec)
>    passed  11/38  mod-test-nanoseconds (0.000774 sec)
>    passed  12/38  mod-test-non-local-exit-funcall-normal (0.000384 sec)
>    passed  13/38  mod-test-non-local-exit-funcall-signal (0.000350 sec)
>    passed  14/38  mod-test-non-local-exit-funcall-throw (0.000381 sec)
>    passed  15/38  mod-test-non-local-exit-signal-test (0.368848 sec)
>    passed  16/38  mod-test-non-local-exit-throw-test (0.006130 sec)
>    passed  17/38  mod-test-sleep-until (0.203062 sec)
>    passed  18/38  mod-test-string-a-to-b-test (0.000668 sec)
>    passed  19/38  mod-test-sum-docstring (0.000253 sec)
>    passed  20/38  mod-test-sum-test (0.000665 sec)
>    passed  21/38  mod-test-userptr-fun-test (0.000466 sec)
>    passed  22/38  mod-test-vector-test (0.009041 sec)
>    passed  23/38  module--func-arity (0.004958 sec)
>    passed  24/38  module--help-function-arglist (0.000791 sec)
> 2021 Oct 25 08:52:59 emba kernel BUG at /build/linux-Pv5wqf/linux-4.4.0/mm/memory.c:3214!
> 2021 Oct 25 08:52:59 emba RIP  [<ffffffff811cd1ae>] handle_mm_fault+0x13de/0x1b80
> --8<---------------cut here---------------end--------------->8---
>

That looks even weirder. Does the "kernel BUG" line indicate an actual
Linux kernel bug? That could at least explain the weird behavior that
we see in userspace.





  parent reply	other threads:[~2021-10-31 18:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 19:13 bug#50902: 28.0.50; emacs-module-tests time out Michael Albinus
2021-10-08 11:43 ` Michael Albinus
2021-10-09 17:17   ` Philipp Stephani
2021-10-11 16:47     ` Michael Albinus
2021-10-18 14:09       ` Michael Albinus
2021-10-25 12:57         ` Michael Albinus
2021-10-31 17:44           ` Michael Albinus
2021-10-31 18:10           ` Philipp Stephani [this message]
2021-10-31 18:32             ` Michael Albinus
2021-11-12 12:45               ` Philipp
2021-11-12 15:08                 ` Michael Albinus
2021-11-12 18:07                   ` Philipp Stephani
2021-11-14 14:48                     ` Michael Albinus
2021-11-14 15:25                       ` Philipp
2021-11-18 18:41                         ` Michael Albinus
2021-11-19  9:15                           ` Michael Albinus
2021-10-31 18:08         ` Philipp Stephani

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=CAArVCkSRtzEDRnLK9FvKN02WEXNYfsE-DT7cK2ZvMhF-PvjwBg@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=50902@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=phst@google.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).