From: Alyssa Ross <hi@alyssa.is>
To: notmuch@notmuchmail.org
Cc: Puck Meerburg <puck@puckipedia.org>
Subject: T568-lib-thread is non-deterministic
Date: Thu, 14 Jan 2021 15:59:20 +0000 [thread overview]
Message-ID: <871reno6g7.fsf@alyssa.is> (raw)
T568-lib-thread assums that there will always be a thread with ID
thread:0000000000000009, but this turns out not to be the case.
This was reported to us in Nixpkgs[1], where it caused builds of our
notmuch package to intermittently fail, and I was able to
(intermittently) reproduce. We are going to work around this problem
for now by disabling T568. I can provide a Xapian DB generated by this
test with no thread with that ID if that's helpful. I believe this also
explains this report previously sent to the Notmuch mailing list[2].
Note on reproducing: I found that it often would succeed repeatedly
many, many times before failing, and then failing consistently for a
while. My co-conspirator Puck (CCed) thinks this might be due to how
directory order works in ZFS (which just happens to be the filesystem we
are using).
[1]: https://github.com/NixOS/nixpkgs/issues/109092
[2]: https://nmbug.notmuchmail.org/nmweb/show/874ko8trhk.fsf%40tethera.net
next reply other threads:[~2021-07-30 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 15:59 Alyssa Ross [this message]
2021-01-14 16:05 ` T568-lib-thread is non-deterministic Alyssa Ross
2021-07-30 13:17 ` 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=871reno6g7.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=notmuch@notmuchmail.org \
--cc=puck@puckipedia.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).