From: David Bremner <bremner@unb.ca>
To: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>,
Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: T460: new sporadic failures with emacs 29
Date: Fri, 1 Sep 2023 10:27:54 +0000 [thread overview]
Message-ID: <87sf7ykx1y.fsf@motzkin.cs.unb.ca> (raw)
In-Reply-To: <CAA19uiQwzP+tXJdYf_3q+=gaX27gAz2W6R6Bo0LPLXCUx+fzoA@mail.gmail.com>
Michael J Gruber <michaeljgruber+grubix+git@gmail.com> writes:
>
> Yes, that's why I wrote "ignore". Something like NOTMUCH_IGNORE_TESTS
> which runs the test, outputs the diff on fail, but "succeeds" without
> counting towards pass/fail, and reports the number of ignored
> pass/fail separately - basically "known_broken" without the
> "known/expectation".
>
> I just don't know whether it's worth it. Other folks disable a whole
> test suite when they want to get a package update going ...
I guess it would be mainly interesting for distro packagers, or I guess
people who wanted to run come kind of CI.
Without looking at the code, I think just ignoring the return value
would be relatively easy, while keeping track of ignored tests might be
a bit more work. Maybe Tomi has a clearer idea / finds this a fun
problem.
d
prev parent reply other threads:[~2023-09-01 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 11:04 T460: new sporadic failures with emacs 29 Michael J Gruber
2023-08-24 13:15 ` David Bremner
2023-08-24 14:01 ` David Bremner
2023-08-24 14:09 ` Michael J Gruber
2023-08-24 15:10 ` David Bremner
2023-08-24 16:10 ` Michael J Gruber
2023-08-25 22:28 ` David Bremner
2023-08-26 14:20 ` Michael J Gruber
2023-08-26 14:41 ` David Bremner
2023-08-26 19:22 ` Michael J Gruber
2023-08-31 13:15 ` David Bremner
2023-08-31 14:54 ` Michael J Gruber
2023-08-31 15:17 ` David Bremner
2023-09-01 7:31 ` Michael J Gruber
2023-09-01 10:27 ` David Bremner [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf7ykx1y.fsf@motzkin.cs.unb.ca \
--to=bremner@unb.ca \
--cc=michaeljgruber+grubix+git@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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://yhetil.org/notmuch.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).