From: Ruud van der Pas <ruud.vanderpas@oracle.com>
To: Jose Marchesi <jose.marchesi@oracle.com>
Cc: Jan Beulich via Binutils <binutils@sourceware.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: gprofng not quite ready for prime time?
Date: Thu, 11 Aug 2022 11:43:21 +0000 [thread overview]
Message-ID: <EFEA3506-BF87-468B-B531-A1E154E3613A@oracle.com> (raw)
In-Reply-To: <87h72kuzlg.fsf@oracle.com>
Hi Jan and José,
Thanks for your postings on this.
>> Earlier this year (iirc) some overly long lasting gas tests have been
>> disabled / altered. None of those took minutes. So I'm inclined to say
>> that anything which takes longer than a couple of seconds should be
>> off by default. Of course the threshold lowers as more tests are added,
>> unless a way is found to parallelize their running.
>
> I think this is a sensible approach.
I think so too.
> We could have an additional check-expensive (or similar) target to run
> the full testsuite.
Right. Maybe not associate this with money though ;-)
Perhaps something like "check-extensive" and issue a message how long
we expect those tests to run. Certainly also provide feedback.
Nothing worse than a terminal prompt that doesn't re-appear for a
long long time after all!
We're very keen to address this and as a starting point, I just submitted
a bug report on this:
Bug 29470 - [test suite] The test suite should be made more flexible
https://sourceware.org/bugzilla/show_bug.cgi?id=29470
I also submitted a bug report against the version.texi file. In retrospect,
I think it is overkill to generate this file. We should just make sure
to update it with the new info when we release a doc patch.
This is the bug id by the way:
Bug 29465 - [docs] File version.texi is created in the binutils source directory
https://sourceware.org/bugzilla/show_bug.cgi?id=29465
Kind regards, Ruud
next prev parent reply other threads:[~2022-08-11 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:57 Jan Beulich
2022-08-09 14:33 ` Luis Machado
2022-08-09 18:17 ` Ruud van der Pas
2022-08-10 6:58 ` Jan Beulich
2022-08-10 11:06 ` Jose E. Marchesi
2022-08-11 11:43 ` Ruud van der Pas [this message]
2022-08-11 12:23 ` Jan Beulich
2022-08-11 14:02 ` Ruud van der Pas
2022-08-11 14:23 ` Jan Beulich
2022-08-11 15:41 ` Ruud van der Pas
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=EFEA3506-BF87-468B-B531-A1E154E3613A@oracle.com \
--to=ruud.vanderpas@oracle.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jose.marchesi@oracle.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).