Re: Bug: fatal error with notmuch new, second run starts indexing all over again

Subject: Re: Bug: fatal error with notmuch new, second run starts indexing all over again

Date: Fri, 14 Jul 2017 23:27:03 +0200

To: notmuch

Cc:

From: Gregor Zattler


Hi David,
* David Bremner <david@tethera.net> [14. Jul. 2017]:
> Gregor Zattler <telegraph@gmx.net> writes:
>> 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.

I would assume the first difference is in the file system:
Perhaps the files are accessed in a different order!?

> Anyway, now that I have a test case, I'll try and figure out what the
> underlying Xapian exeception is.


Thanks.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-


Thread: