all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Michael Albinus <Michael.Albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Flickering tests
Date: Wed, 03 Jul 2024 14:16:44 -0400	[thread overview]
Message-ID: <yp134oqjq7n.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8734oqh4d2.fsf@gmx.de> (Michael Albinus's message of "Wed, 03 Jul 2024 17:39:21 +0200")

Michael Albinus <Michael.Albinus@gmx.de> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
> Hi Andrea,
>
>> Mmhh, I've the impression this happen on my system only when it's under
>> heavy load.  I've 64 cores and if I "make check -j64" I've say 50%
>> probability to hit these, but if I run only:
>>
>> ./src/emacs -batch -l ert -l ./test/lisp/net/dbus-tests.el -f ert-run-tests-batch-and-exit
>>
>> they all pass.  Perhaps some timeout need to be adjusted?
>
> It's not the a I believe. D-Bus tests are sending events to the D-Buson
> OS level, and receiving events which will be interpreted. They are not
> written such a way that all tests can run in parallel.
>
> If you invoke "make check -j64", it could happen that some D-Bus tests
> run in parallel, and returning events do arrive in another Emacs
> instance but the one which has send the evnt. This might be even more
> problematic, because recently (on Sunday, commit
> 4e22ef870c4b650f29c4441ac51b6a2ac506ea57) a test which registers for
> wildcard events has been added. This test resides in my local Emacs git
> for 3 months w/o problems; I've simply waited until the FSF papers of
> the author, Robert Church, were on file.
>
> What could we do? Could we exclude dbus-tests.el from running as
> simultaneous job?

Mmmh not sure is possible but also desirable, we want to be able to run
as many tests as possible even with -jN.

> Or could we simply skip D-Bus tests, if we detect that the tests run via
> simultaneous make jobs? How to check, on Lisp level?

Perhaps using some lock file as mutex for the generation of D-Bus
messages from different test files?

> We always have the option to mark this test as :unstable, so we could
> stabilize the Emacs 30 release this way. But it would be a pity.
>
> Btw, could you check whether the D-Bus tests flickery goes away if we
> tag dbus-test05-register-signal-with-nils as :unstable?

From the bunch of test I did seems this is solving, I'll mark it as
:unstable for now till a better solution is found.

Thanks

  Andrea



  reply	other threads:[~2024-07-03 18:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  9:47 Flickering tests Andrea Corallo
2024-07-02 12:43 ` Andrea Corallo
2024-07-03  1:47   ` john muhl
2024-07-03  7:25     ` Andrea Corallo
2024-07-03 20:14       ` Stefan Kangas
2024-07-04 19:41         ` john muhl
2024-07-02 14:28 ` Michael Albinus
2024-07-02 15:25   ` Andrea Corallo
2024-07-03 14:52     ` Andrea Corallo
2024-07-03 15:39       ` Michael Albinus
2024-07-03 18:16         ` Andrea Corallo [this message]
2024-07-05  7:36           ` Michael Albinus
2024-07-09  8:39             ` Andrea Corallo
2024-07-09  8:49               ` Michael Albinus
2024-07-09  9:47                 ` Andrea Corallo
2024-07-09 10:47                   ` Michael Albinus
2024-07-09 12:30                     ` Andrea Corallo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp134oqjq7n.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=Michael.Albinus@gmx.de \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.