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 CAFCA6DE0FFA for ; Tue, 23 Apr 2019 18:09:29 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.028 X-Spam-Level: X-Spam-Status: No, score=-0.028 tagged_above=-999 required=5 tests=[AWL=-0.027, SPF_PASS=-0.001] 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 0NMG-HTqEpZ0 for ; Tue, 23 Apr 2019 18:09:28 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id BCF366DE0F44 for ; Tue, 23 Apr 2019 18:09:28 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hJ6Pc-0006JM-Su; Tue, 23 Apr 2019 21:09:24 -0400 Received: (nullmailer pid 20385 invoked by uid 1000); Wed, 24 Apr 2019 01:09:23 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: subsequent rebuilds of notmuch always re-build sphinx and ruby In-Reply-To: <87tveotn1g.fsf@fifthhorseman.net> References: <87r29wwgq2.fsf@fifthhorseman.net> <87a7gkdxns.fsf@tethera.net> <87d0lgvylb.fsf@fifthhorseman.net> <87mukjcg3l.fsf@tethera.net> <87h8apvda4.fsf@fifthhorseman.net> <875zr5d1vq.fsf@tethera.net> <87tveotn1g.fsf@fifthhorseman.net> Date: Tue, 23 Apr 2019 22:09:23 -0300 Message-ID: <87r29sb458.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Wed, 24 Apr 2019 01:09:29 -0000 Daniel Kahn Gillmor writes: > On Mon 2019-04-22 21:03:05 -0300, David Bremner wrote: >> There was a problem with the first patch, which I replaced with two more. > > thanks. i've reviewed and published my review on that series. I think > it should probably be merged. > >> I'm open to ideas, but keep in mind we want to support parallel make, >> which means we have to be careful not to trigger multiple invocations of >> sphinx-build in parallel. > hm, i'm not entirely sure why sphinx-build can't be run in parallel, if > it could target the creation of specific files (but maybe it can't). It can target specific files according to the documentation, but the main issue is that it caches a bunch of state under doc/_build/doctrees. It doesn't do any kind of locking, so multiple writers leads to build failures. > > I do note that (independent of this series), if i run the following > loop: > > > while make -j4 --trace; do > python3 -c 'print("="*100)' > touch doc/man1/notmuch-reply.rst > done > > then only every second run of make contains this info: > I think I see this also, but no idea yet what is going on.