unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: T460: new sporadic failures with emacs 29
Date: Thu, 24 Aug 2023 18:10:43 +0200	[thread overview]
Message-ID: <CAA19uiQ6QRLFm3VfueQ=35DcGNcGgkqEW7A-UFAdcn0br2oKmA@mail.gmail.com> (raw)
In-Reply-To: <87v8d45ve8.fsf@tethera.net>

Am Do., 24. Aug. 2023 um 17:10 Uhr schrieb David Bremner <david@tethera.net>:
>
> David Bremner <david@tethera.net> writes:
>
> > I just saw this when running in debian's "sbuild" isolated build
> > environment. So my current guess is that this has to do with HOME
> > pointing somewhere nonexistent. Is that also the case in COPR?
> >
> > d
>
> I realized that we override HOME inside the tests anyway, so emacs
> should think there is some writable HOME in any case. I did notice that
> the tests trigger a bunch of emacs native compilation (because the
> caching happens in the temporary $HOME, which gets blown away every
> time).

Also, $HOME is set in all my build envs (pass or fail), and
permissions are the same. Bummer.

It took more runs to get some fails now, and archs vary, so I still
think its a time out. And no way to get it locally so far.

ENOLISP (for me) but could it be the case that notmuch-test-wait can
abort its while loop too early if the first buffer write takes longer
than the timeout, or if some other process writes (because the process
parameter is nil)? Is something different for emacs 29 in this regard?
Any clues from sbuild?

Michael

  reply	other threads:[~2023-08-24 16:11 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 [this message]
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

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='CAA19uiQ6QRLFm3VfueQ=35DcGNcGgkqEW7A-UFAdcn0br2oKmA@mail.gmail.com' \
    --to=michaeljgruber+grubix+git@gmail.com \
    --cc=david@tethera.net \
    --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).