From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: work around xapian bug with get_mset(0,0, x)
Date: Sun, 15 Apr 2018 19:54:16 +0300 [thread overview]
Message-ID: <m2604ss953.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20180406114307.7067-1-david@tethera.net>
On Fri, Apr 06 2018, David Bremner wrote:
> At least Fedora28 triggers this Xapian bug due to some toolchain change .
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1546162
>
> The underlying bug is fixed in xapian commit f92e2a936c1592, and
> should be fixed in Xapian 1.4.6
> ---
>
> I have verified this doesn't break the test suite in my environment,
> but I would appreciate feedback from someone with a Fedora 28 test
> platform.
Without this change, on Fedora 28 container:
9 aborts.
test execution halts at T570-revision-tracking.2 since ${result}
is empty string
with this change: failure count is about the same as with fedora 27
so, +1
That, is my setup, pulled fedora:28 docker image and run a script
to install some stuff there. I'd bet I can get the error count
down by tuning the creation script...
Tomi
next prev parent reply other threads:[~2018-04-15 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 11:43 [PATCH] lib: work around xapian bug with get_mset(0,0, x) David Bremner
2018-04-15 16:54 ` Tomi Ollila [this message]
2018-04-18 0:07 ` [PATCH] NEWS: news item for mset fix David Bremner
2018-04-18 6:59 ` Tomi Ollila
2018-04-18 19:04 ` [PATCH] lib: work around xapian bug with get_mset(0,0, x) Daniel Kahn Gillmor
2018-04-18 23:13 ` David Bremner
2018-04-19 14:12 ` Daniel Kahn Gillmor
2018-04-20 12:53 ` David Bremner
2018-04-27 1:53 ` David Bremner
2018-04-27 1:53 ` David Bremner
2018-04-28 14:34 ` 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=m2604ss953.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--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).