From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 26B943858D28 for ; Wed, 18 Jan 2023 15:01:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 26B943858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674054110; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ltGBXA/eIV24a+9N3ABifGMeYMMfZZ/GibWVedGeAmU=; b=UQact/0tqDBOtEfiDkD/jSI6sEoyTfvhKL7UjCt7w0EN85PdH0UAUF/r/jfXfCWNgkaGA/ Ory2owPZZbpcTlRjVmMwOT9vKBi+0BEoXO4xMFF1TGMhkro/uxqZfNrRPMrJMTZR+mjN5Z xpy5C0mCj1B97kdYce2xLXY6pMrIJM8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-124-bHVoncbTNGuIvtm7DumRoA-1; Wed, 18 Jan 2023 10:01:44 -0500 X-MC-Unique: bHVoncbTNGuIvtm7DumRoA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0C652183B3D0; Wed, 18 Jan 2023 15:01:41 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.56]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EFE3F51E5; Wed, 18 Jan 2023 15:01:40 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1pI9wZ-00067Z-RN; Wed, 18 Jan 2023 10:01:40 -0500 Date: Wed, 18 Jan 2023 10:01:39 -0500 From: "Frank Ch. Eigler" To: Arsen =?utf-8?Q?Arsenovi=C4=87?= Cc: bunsen@sourceware.org, builder@sourceware.org Subject: Re: Automake dist-check and log extraction: runtest --outdir Message-ID: <20230118150139.GD10730@redhat.com> References: <86sfg8iw7d.fsf@aarsen.me> <20230117235107.GC10730@redhat.com> <86ilh4itbq.fsf@aarsen.me> MIME-Version: 1.0 In-Reply-To: <86ilh4itbq.fsf@aarsen.me> User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - > [...] > I didn't mean to emphasize the role of inotify at all, rather the role > of distchecks cleanup of the build directory, which acts as a limit on > the lifetime of the testsuite results file. > > The builder could avoid testsuite files being deleted altogether by > specifying an outdir outside of distchecks temporary directory. Ah yes, we have encountered this annoying behaviour before. OK, so those build jobs that run "make distcheck" in anger could use "make distcheck RUNTESTFLAGS=--outdir=../foobar" to preserve test results across the implicit "make distclean". - FChE