From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 4B7C36DE271B for ; Fri, 14 Jul 2017 04:13:38 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZgTvIYkn40n for ; Fri, 14 Jul 2017 04:13:37 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 9A94E6DE2709 for ; Fri, 14 Jul 2017 04:13:37 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dVyUD-0003FY-2h; Fri, 14 Jul 2017 07:10:17 -0400 Received: (nullmailer pid 8059 invoked by uid 1000); Fri, 14 Jul 2017 11:13:33 -0000 From: David Bremner To: Gregor Zattler , notmuch Subject: Re: Bug: fatal error with notmuch new, second run starts indexing all over again In-Reply-To: <20170714101436.dnacwh3rbwva5htp@len.workgroup> References: <20170703220750.dkornyh4ho7b2azy@len.workgroup> <87inj9w3nu.fsf@tethera.net> <20170706093101.cdjxdgvfy57a3kkb@len.workgroup> <87o9st3hz0.fsf@tethera.net> <20170709142147.czeett6stskxrnkp@len.workgroup> <87k23h3cgg.fsf@tethera.net> <20170713070444.tr4n2yfot5t4j663@len.workgroup> <87bmooebfs.fsf@tethera.net> <20170713135947.nqdagxnxe5sdubko@len.workgroup> <87y3rsp517.fsf@tesseract.cs.unb.ca> <20170714101436.dnacwh3rbwva5htp@len.workgroup> Date: Fri, 14 Jul 2017 08:13:33 -0300 Message-ID: <878tjre0f6.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 11:13:38 -0000 Gregor Zattler 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. d