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.129.124]) by sourceware.org (Postfix) with ESMTPS id 658603858D35 for ; Tue, 17 Jan 2023 23:51:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 658603858D35 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=1673999474; 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=OwiiiJerY1cfnncbHXCeJmmGO1aNI4/wQGmhhIS6z/w=; b=Yccvrxh+3RSRrWCPaKK3K1re3Ookj0U5q2/dT7gnyfSvvYDOWuYbdjgIjUxdttXilXunfw dRL1yGlVZgUPzjedk//+haN/2zZbHi6D2KRfZJRiez+XhYrhCX49vOMc0JWOihXLOr7c6W QdN0mWBsu2g3rrLdahuwlATIHczMyzs= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-669-nK0Foj1hOjak5AD43Z9dFA-1; Tue, 17 Jan 2023 18:51:09 -0500 X-MC-Unique: nK0Foj1hOjak5AD43Z9dFA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B4BDC2804123; Tue, 17 Jan 2023 23:51:08 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.56]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A507CC15BAD; Tue, 17 Jan 2023 23:51:08 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1pHvjP-00051o-O8; Tue, 17 Jan 2023 18:51:07 -0500 Date: Tue, 17 Jan 2023 18:51:07 -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: <20230117235107.GC10730@redhat.com> References: <86sfg8iw7d.fsf@aarsen.me> MIME-Version: 1.0 In-Reply-To: <86sfg8iw7d.fsf@aarsen.me> User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 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=-8.1 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=unavailable 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 - > The make_distcheck_test_suite_step uses a logfiles= keyword arg, which > in turn uses inotify (presumably) to watch a file for a logfile creatd > on it, and to collect info from it. buildbot buildbot_worker runprocess.py appears to use fstat ctime/mtime/size polling to query in-progress files. bunsen only collects final files. > [...] > DejaGnu provides a way for the directory in which log and sum files are > stored to be altered, see --outdir in > [...] > This, indeed, resulted in a poke.log and poke.sum in the /tmp/outtest > directory. > I believe we should replace the inotify-based mechanism with this method > of redirecting logs. I'm afraid I don't quite understand how this should improve on anything, even if buildbot-worker were to use inotify instead of fstat polling. It's just a different pathname for the files. - FChE