From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: David Bremner <bremner@unb.ca>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: T460: new sporadic failures with emacs 29
Date: Thu, 31 Aug 2023 16:54:59 +0200 [thread overview]
Message-ID: <CAA19uiR37XLJJmHaPs7ndN6_gfJEeLXB1huoXZvc3nBRXJFE_A@mail.gmail.com> (raw)
In-Reply-To: <87ledrqrn5.fsf@motzkin.cs.unb.ca>
Am Do., 31. Aug. 2023 um 15:16 Uhr schrieb David Bremner <bremner@unb.ca>:
>
> Michael J Gruber <michaeljgruber+grubix+git@gmail.com> writes:
>
> > Am Sa., 26. Aug. 2023 um 16:41 Uhr schrieb David Bremner <david@tethera.net>:
> >>
> >> Michael J Gruber <michaeljgruber+grubix+git@gmail.com> writes:
> >>
> >> >
> >> > I tried the current 0.38rc1 on COPR, and unfortunately I get the same
> >> > T460 failure (fedora-eln-aarch64 and fedora-rawhide-x86_64 this time,
> >> > out of 35 buildroots).
> >> > Did you get your fails with emacs 29 only, or with earlier emacs?
> >>
> >> I only tested emacs 29; it would be some different incantation to
> >> semi-disable native compilation for emacs 28.x. Are you seeing those
> >> same failures (where emacs attempting to write into /usr/bin) on older
> >> emacs?
> >
> > No, I see them only on Fedora rawhide/ELN and Fedora 39, but not on
> > the current release 38 or earlier. Emacs 29/28 is one difference and
> > an obvious guess as the cause, but it could be dtach or whatnot.
>
> Hmm. I just built 200 times in sbuild (chroot) so I guess I am no longer
> able to reproduce the issue on Debian, fwiw.
I still get those issues. OTOH, skipping T460.14 did not show any
adverse side effects. So I'll do that for emacs29.
I might be nice to mark some tests ignored rather than skipped so that
we notice when they do not fail sporadically any more. That is, *if*
we look at the output of a passing test suite ...
Michael
next prev parent reply other threads:[~2023-08-31 14:55 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 [this message]
2023-08-31 15:17 ` David Bremner
2023-09-01 7:31 ` Michael J Gruber
2023-09-01 10:27 ` David Bremner
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=CAA19uiR37XLJJmHaPs7ndN6_gfJEeLXB1huoXZvc3nBRXJFE_A@mail.gmail.com \
--to=michaeljgruber+grubix+git@gmail.com \
--cc=bremner@unb.ca \
--cc=notmuch@notmuchmail.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://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).