From: Hans-Peter Nilsson <hp@bitrange.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)
Date: Wed, 3 Jan 2024 23:59:36 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2401032353040.30514@arjuna.pair.com> (raw)
In-Reply-To: <65962398.9060100@gmail.com>
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
next prev parent reply other threads:[~2024-01-04 4:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 14:04 [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor Maciej W. Rozycki
2023-12-12 14:04 ` [PATCH DejaGNU 1/1] " Maciej W. Rozycki
2023-12-12 23:02 ` Jeff Law
2023-12-13 3:48 ` Jacob Bachmeyer
2023-12-12 14:04 ` [PATCH GCC 1/1] testsuite: Support test execution timeout factor as a keyword Maciej W. Rozycki
2023-12-12 23:03 ` Jeff Law
2024-01-03 5:15 ` [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor Hans-Peter Nilsson
2024-01-03 16:38 ` Maciej W. Rozycki
2024-01-03 23:00 ` Richard Sandiford
2024-01-04 3:18 ` Generalizing DejaGnu timeout scaling (was: Re: [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor) Jacob Bachmeyer
2024-01-04 4:59 ` Hans-Peter Nilsson [this message]
2024-01-05 2:27 ` Generalizing DejaGnu timeout scaling Jacob Bachmeyer
2024-01-04 4:52 ` [PATCH DejaGNU/GCC 0/1] Support per-test execution timeout factor Hans-Peter Nilsson
2024-02-01 20:18 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.20.16.2401032353040.30514@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=dejagnu@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jcb62281@gmail.com \
--cc=macro@embecosm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).