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 A0B806DE0F39 for ; Tue, 21 May 2019 13:23:29 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.429 X-Spam-Level: X-Spam-Status: No, score=0.429 tagged_above=-999 required=5 tests=[AWL=-0.223, SPF_NEUTRAL=0.652] 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 bRnumRkYF6ss for ; Tue, 21 May 2019 13:23:28 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by arlo.cworth.org (Postfix) with ESMTP id C37C46DE0EDB for ; Tue, 21 May 2019 13:23:27 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id 9F5D81000D0; Tue, 21 May 2019 23:23:25 +0300 (EEST) From: Tomi Ollila To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: [PATCH] test: avoid hanging older gdb under GNU timeout and moreutils parallel In-Reply-To: <87blzvajt6.fsf@fifthhorseman.net> References: <87mujgab6j.fsf@fifthhorseman.net> <20190521010304.417-1-dkg@fifthhorseman.net> <87blzvajt6.fsf@fifthhorseman.net> User-Agent: Notmuch/0.28.3+84~g41389bb (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ 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: Tue, 21 May 2019 20:23:29 -0000 On Tue, May 21 2019, Daniel Kahn Gillmor wrote: > Hi Tomi-- > > On Tue 2019-05-21 09:12:12 +0300, Tomi Ollila wrote: >> This looks like a good read: >> https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_21.html >> and is used to speculate below. > > Thanks for this pointer, and for the additional analysis. > > While i understand this problem much better than i did two days ago, i'm > not sure whether there is an alternate proposal here for how to handle > the situation. Do you have a suggestion for some other fix? I hope id:20190521201702.28754-1-tomi.ollila@iki.fi works Tomi > > It's tempting to remove the "controlling terminal" from the test suite > entirely (e.g. by running it under "setsid --wait"), but i'm reluctant > to do so because that is not the context in which most instances of > notmuch will themselves be run, and i don't really want the test suite > to be so alienated. Every test script itself, if not already setsid(1)ed would need to re-exec itself w/ that, then. (as I can now run e.g. ./T380-atomicity.sh directly from command line) > > So i'm unsure what to do, but i do want to try to move on beyond all > this "testing the test suite" and start getting more e-mail-related > features into notmuch again :P > > --dkg