From: Xiyue Deng <manphiz@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mattiase@acm.org, 66782@debbugs.gnu.org
Subject: bug#66782: 29.1; ERT tests report test redefined depending on loading sequence
Date: Sat, 28 Oct 2023 12:41:19 -0700 [thread overview]
Message-ID: <871qdeh6w0.fsf@debian-hx90.lan> (raw)
In-Reply-To: <83h6mbc5ss.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Oct 2023 15:03:47 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Xiyue Deng <manphiz@gmail.com>
>> Cc: mattiase@acm.org, 66782@debbugs.gnu.org
>> Date: Sat, 28 Oct 2023 04:50:37 -0700
>>
>> P.S. I also thought of another potential counter-example of preferring
>> running one test file over running many in one batch: the tests within
>> the same test file may also leave garbage for the rest of the tests
>
> We could reasonably expect from the author of a single .el test file
> to make sure the tests in that file don't interfere with one another
> and make the necessary cleanups for that purpose. But it is much
> harder to expect the same from several disparate test files, which can
> quite frequently be written and maintained by different people.
Fair enough. And of course ideally each test should be able to run
either independently and batched together so that running everything in
batch is possible with the nice summary :-)
--
Xiyue Deng
prev parent reply other threads:[~2023-10-28 19:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:59 bug#66782: 29.1; ERT tests reports test redefined depending on loading sequence Xiyue Deng
2023-10-28 6:32 ` Eli Zaretskii
2023-10-28 9:39 ` bug#66782: 29.1; ERT tests report " Xiyue Deng
2023-10-28 9:48 ` Eli Zaretskii
2023-10-28 11:14 ` Xiyue Deng
2023-10-28 11:34 ` Eli Zaretskii
2023-10-28 11:50 ` Xiyue Deng
2023-10-28 12:03 ` Eli Zaretskii
2023-10-28 12:46 ` Mattias Engdegård
2023-10-28 21:19 ` Xiyue Deng
2023-10-29 12:09 ` Mattias Engdegård
2023-10-29 21:53 ` Xiyue Deng
2023-10-30 12:04 ` Mattias Engdegård
2023-10-30 20:47 ` Xiyue Deng
2023-11-02 17:17 ` Xiyue Deng
2023-11-02 18:56 ` Mattias Engdegård
2023-11-02 22:00 ` Xiyue Deng
2023-11-03 17:14 ` Mattias Engdegård
2023-11-03 17:56 ` Xiyue Deng
2023-11-04 8:51 ` Eli Zaretskii
2023-10-28 19:41 ` Xiyue Deng [this message]
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=871qdeh6w0.fsf@debian-hx90.lan \
--to=manphiz@gmail.com \
--cc=66782@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.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 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).