From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=JGCq=IO=bitrange.com=hp@sourceware.org>
Received: from arjuna.pair.com (arjuna.pair.com [209.68.5.131])
	by sourceware.org (Postfix) with ESMTPS id B5B213858D32
	for <gcc-patches@gcc.gnu.org>; Thu,  4 Jan 2024 04:59:36 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B5B213858D32
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bitrange.com
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=bitrange.com
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org B5B213858D32
Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=209.68.5.131
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1704344378; cv=none;
	b=YQ/ai5FLRXpi9wvf31HVc0004/klWIYN9aOHREF1aGKzgAYkUGOd0bK+62z3kPFyexUrTEc1YQBm1mz9ZBRM+lcuKJDQKfRDUs6fo+rwlpvAWLuo4JNfTxdNA/FrmqlZ4J2Gg0GXO2/Mg+Tv4EzIc5HSZvxw82jXN0q2HMZhI+E=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1704344378; c=relaxed/simple;
	bh=xUJrvUc7BnpmCYgwl8Bh7iWuo1WnNX8VAAqOM/HuD+8=;
	h=Date:From:To:Subject:Message-ID:MIME-Version; b=CuPi1zCuB98te7i6HzRtq/2t2e5Fu4SWa6oERqx1k0jYwYH07FSMN7S8AUjItUFvpB8QNwyHZ0ZT902MbmFe76klWVE40bGoB4bSL+wMuOcg+hsc8F8VAv6GRdZEzM6G1XrW5oFb8RGZYotBt6xED92KPKPX4XXnQ2caRp7AaJQ=
ARC-Authentication-Results: i=1; server2.sourceware.org
Received: by arjuna.pair.com (Postfix, from userid 3006)
	id 83CA48A64F; Wed,  3 Jan 2024 23:59:36 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by arjuna.pair.com (Postfix) with ESMTP id 832F08A597;
	Wed,  3 Jan 2024 23:59:36 -0500 (EST)
Date: Wed, 3 Jan 2024 23:59:36 -0500 (EST)
From: Hans-Peter Nilsson <hp@bitrange.com>
X-X-Sender: hp@arjuna.pair.com
To: Jacob Bachmeyer <jcb62281@gmail.com>
cc: "Maciej W. Rozycki" <macro@embecosm.com>, dejagnu@gnu.org, 
    gcc-patches@gcc.gnu.org
Subject: Re: Generalizing DejaGnu timeout scaling (was: Re: [PATCH DejaGNU/GCC
 0/1] Support per-test execution timeout factor)
In-Reply-To: <65962398.9060100@gmail.com>
Message-ID: <alpine.BSF.2.20.16.2401032353040.30514@arjuna.pair.com>
References: <alpine.DEB.2.20.2312111744390.5892@tpp.orcam.me.uk> <alpine.BSF.2.20.16.2401030005590.40261@arjuna.pair.com> <alpine.DEB.2.20.2401031602140.5892@tpp.orcam.me.uk> <65962398.9060100@gmail.com>
User-Agent: Alpine 2.20.16 (BSF 172 2016-09-29)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Scanned-By: mailmunge 3.11 on 209.68.5.131
X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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: <gcc-patches.gcc.gnu.org>

On Wed, 3 Jan 2024, Jacob Bachmeyer wrote:
> Comments before I start on an implementation?

I'd suggest to await the conclusion of the debate: I *think* 
I've proved that dg-timeout-factor is already active as intended 
(all parts of a test), specifically when the compilation result 
is executed (for the applicable tests).  Notably, modulo bugs in 
the test-suites.

Of course, it may be useful to separate different timeouts of 
separable parts of a test - compilation and execution being the 
topic at hand.  But IMHO, YAGNI.  Having said that, don't let 
that stand in the way of a fun hack!

brgds, H-P