From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Jan Beulich via Binutils <binutils@sourceware.org>
Subject: Re: gprofng not quite ready for prime time?
Date: Wed, 10 Aug 2022 13:06:51 +0200 [thread overview]
Message-ID: <87h72kuzlg.fsf@oracle.com> (raw)
In-Reply-To: <73d79c76-a602-5da7-43d2-ab93888f2fb6@suse.com> (Jan Beulich via Binutils's message of "Wed, 10 Aug 2022 08:58:50 +0200")
> On 09.08.2022 20:17, Ruud van der Pas wrote:
>>> Initially I merely noticed version.texi trying to be created in the
>>> source tree, which of course won't work if that one is read-only.
>>
>> This is oversight. I will create a bugzilla bug report and address this
>> right away.
>
> Thanks.
>
>>> But then I further noticed that the testsuite fails to build and/or
>>> run various things, first and foremost because of (but not
>>> necessarily limited to) Java not being available.
>>
>> This work was done by Vladimir. He is currently away, but we will look
>> into this no later than this week.
>>
>>> Despite (or maybe
>>> as a result of) this the running of the (mostly failing) testsuite
>>> took a non-negligible amount of time for the just 5 tests (on
>>> x86-64).
>>
>> This is in the nature of the beast. As Luis already mentioned, we run
>> the tests in a fixed amount of time. We do so to get enough samples to
>> verify the functionality.
>>
>> We are definitely interested in addressing this if it is considered to
>> take too much time. For example, make the fixed time a user tunable, with
>> a certain default, or alternatively provide feedback on the expected
>> duration of the test(s) to the builder. Any other suggestion is welcome!
>
> 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.
We could have an additional check-expensive (or similar) target to run
the full testsuite.
next prev parent reply other threads:[~2022-08-10 11:07 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 [this message]
2022-08-11 11:43 ` Ruud van der Pas
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=87h72kuzlg.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=binutils@sourceware.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).