From: Karl Berry <karl@freefriends.org>
To: simon@josefsson.org
Cc: marc.nieper+gnu@gmail.com, bug-gnulib@gnu.org, bruno@clisp.org,
48113@debbugs.gnu.org
Subject: Re: bug#48113: Module suggestion: timeout
Date: Sat, 1 May 2021 15:13:00 -0600 [thread overview]
Message-ID: <202105012113.141LD0kr031717@freefriends.org> (raw)
In-Reply-To: <878s50dt1n.fsf@latte.josefsson.org>
What do bug-automake people think?
For myself, I have no objection to sprinkling timeout commands through
the Automake test infrastructure wherever appropriate. It's not ever
going to rise to the top of my own list of things to do, though, so if
it's going to happen, you or someone will have to write the patch.
Of course I don't speak for Jim, but from what he's said in the past,
I suspect he is in a similar situation.
No one else has come forward to work on Automake, despite my plea
(https://lists.gnu.org/archive/html/automake/2021-03/msg00018.html),
so I guess that's where we are.
the functionality could be opt-in initially,
Certainly.
and then after a few years become the default behaviour.
Personally, I think it should be opt-in forever. People could easily
have test suites that need to run for days. I prefer not to
unnecessarily break compatibility.
Thanks,
Karl
next prev parent reply other threads:[~2021-05-01 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 12:22 Module suggestion Marc Nieper-Wißkirchen
2021-04-29 14:19 ` Module suggestion: timeout Bruno Haible
2021-04-30 9:24 ` Simon Josefsson via Gnulib discussion list
2021-04-30 9:37 ` Marc Nieper-Wißkirchen
2021-04-30 9:43 ` Simon Josefsson via Gnulib discussion list
2021-04-30 9:47 ` Marc Nieper-Wißkirchen
2021-05-01 21:13 ` Karl Berry [this message]
2021-05-02 7:30 ` bug#48113: " Simon Josefsson via Gnulib discussion list
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202105012113.141LD0kr031717@freefriends.org \
--to=karl@freefriends.org \
--cc=48113@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=marc.nieper+gnu@gmail.com \
--cc=simon@josefsson.org \
/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).