confirmed (was: Bug: fatal error with notmuch new, second run starts indexing all over again)

[Gregor Zattler <telegraph@gmx.net>]

Hi David, notmuch developers,
* David Bremner <david@tethera.net> [2021-12-25; 14:10]:
> David Bremner <david@tethera.net> writes:
>> Gregor Zattler <telegraph@gmx.net> writes:
>>> On my way reducing the corpus I had an intermediate corpus of
>>> ~43000 files on which notmuch new produced a xapian exeption.  I
>>> kept this corpus but did not include the test results in my email
>>> because the later, smaller corpus seemed more interesting.
>>>
>>> I redid the test on this mid-sized corpus and I got an
>>> exeption (again):
>> [snip]
>>> Error: A Xapian exception occurred. Halting processing.
>>> Processed 27611 total files in 21m 2s (21 files/sec.).
>>> Added 27481 new messages to the database.
>>> Note: A fatal error was encountered: A Xapian exception occurred
>>> [Inferior 1 (process 6752) exited with code 01]
>>> (gdb)
>>
>> I can finally replicate the crash. I do crash in a different place
>> (after processing 25184 files), so it suggests a certain non-determinism
>> or dependence on the host configuration.
>>
>> Anyway, now that I have a test case, I'll try and figure out what the
>> underlying Xapian exeception is.
>
> As far as I know this was dixed in xapian 1.4.7, so marking it fixed for
> notmuch.

I redid the test with my mid-sized corpus from the org-mode
mailing liste which used to crash notmuch when indexing.

That's indeed not the case any more with a up to date

- debian 11/bullseye,

- GNU Emacs 29.0.50 (build 3, x86_64-pc-linux-gnu, cairo
  version 1.16.0) of 2021-12-27,

- notmuch 0.34.2+41~g063f5e9

Thank you very much for notmuch, Gregor