From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: notmuch@notmuchmail.org
Subject: T460: new sporadic failures with emacs 29
Date: Thu, 24 Aug 2023 13:04:22 +0200 [thread overview]
Message-ID: <CAA19uiTphvMOGHQx0tMZ2MUTZdNn0AdHAvOvi9_JYzyguARv9A@mail.gmail.com> (raw)
Hi there,
I'm sorry to report that I'm getting new sporadic (some archs
sometimes) failures on Fedora 39+ only, i.e. with emacs 29, on COPR.
```
T460-emacs-tree: Testing emacs tree view interface
PASS Basic notmuch-tree view in emacs
...
PASS Tree view of a single thread (from show)
FAIL Message window of tree view
--- T460-emacs-tree.14.notmuch-tree-show-window 2023-08-24
10:41:07.938464748 +0000
+++ T460-emacs-tree.14.OUTPUT 2023-08-24 10:41:07.938464748 +0000
@@ -1,41 +0,0 @@
-Lars Kellogg-Stedman <lars@seas.harvard.edu> (2009-11-17) (inbox signed)
...
-notmuch@notmuchmail.org
-http://notmuchmail.org/mailman/listinfo/notmuch
*ERROR*: Opening output file: Permission denied, /usr/bin/OUTPUT
PASS Stash id
```
That "/usr/bin/OUTPUT" looks strange and smells like a mis-expanded
variable. Why sporadically, though? The emacs test wait 0.1 before
writing - I dunno why, but those waits are fragile and make me nervous
about even keeping the tests for release builds.
I guess due to its load, COPR is prone to exposing timing issues.
Michael
next reply other threads:[~2023-08-24 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 11:04 Michael J Gruber [this message]
2023-08-24 13:15 ` T460: new sporadic failures with emacs 29 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
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=CAA19uiTphvMOGHQx0tMZ2MUTZdNn0AdHAvOvi9_JYzyguARv9A@mail.gmail.com \
--to=michaeljgruber+grubix+git@gmail.com \
--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).