From: Andrea Corallo <acorallo@gnu.org>
To: john muhl <jm@pub.pink>
Cc: emacs-devel@gnu.org, Michael Albinus <Michael.Albinus@gmx.de>
Subject: Re: Flickering tests
Date: Wed, 03 Jul 2024 03:25:08 -0400 [thread overview]
Message-ID: <yp1zfqzj5t7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87v81nl00w.fsf@pub.pink> (john muhl's message of "Tue, 02 Jul 2024 20:47:11 -0500")
john muhl <jm@pub.pink> writes:
> Andrea Corallo <acorallo@gnu.org> writes:
>
>> Andrea Corallo <acorallo@gnu.org> writes:
>>
>>> Hello,
>>>
>>> lately I see some flickering tests in the testsuite.
>>>
>>> I see these tests failing irregularly on emacs-30 master and igc:
>>>
>>> dbus-test06-register-property-emits-signal
>>> dbus-test05-register-signal-with-nils
>>> dbus-test06-property-types
>>> dbus-test03-peer-interface
>>> secrets-test03-items
>>
>> Forgot to add to the list these two:
>>
>> threads-condvar-wait
>
> I haven’t seen any of the above failing.
>
>> track-changes-tests--random
>
> This one has always been flaky on my test machines.
>
> I also see intermittent failures for:
>
> src/process-tests
> lisp/eshell/esh-cmd-tests
> lisp/eshell/esh-proc-tests
> lisp/eshell/esh-var-tests
> lisp/gnus/mml-sec-tests
> lisp/net/network-stream-tests
> lisp/progmodes/eglot-tests
>
> I assumed these were due to the machines the being underpowered
Mmmh, ideally tests should not be sensitive to the computational power
of the machine.
> but can dig up the logs if someone wants to have a look at them.
I think we should put an effort in reaching a stable a clean testsuite,
should we have separate bugs for each test where we do the
investigation/fix?
next prev parent reply other threads:[~2024-07-03 7:25 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 [this message]
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
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
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=yp1zfqzj5t7.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=Michael.Albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=jm@pub.pink \
/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).