From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
gcc-patches@gcc.gnu.org, Tobias Burnus <tobias@codesourcery.com>,
Mike Stump <mikestump@comcast.net>, Jan Hubicka <hubicka@ucw.cz>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: Support parallel testing in libgomp, part II [PR66005]
Date: Tue, 9 May 2023 19:27:47 +0200 [thread overview]
Message-ID: <20230509192747.5bf23b93@nbbrfq> (raw)
In-Reply-To: <87ednvb1cc.fsf@euler.schwinge.homeip.net>
Thomas,
On Fri, 5 May 2023 10:59:31 +0200
Thomas Schwinge <thomas@codesourcery.com> wrote:
> Worth noting is that with nvptx offloading, there is one execution test case
> that times out ('libgomp.fortran/reverse-offload-5.f90'). This effectively
> stalls progress for almost 5 min:
Short of fixing it for real you could shorten the timeout for this
single test to a handful of seconds: dg-timeout 3
or set it to a 1/50 fraction or the like: dg-timeout-factor 0.02
If it's unbroken then it should run to completion in far less than 10
or 30 seconds, from the looks?
just a thought..
next prev parent reply other threads:[~2023-05-09 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 11:27 [libgomp, testsuite] Support parallel testing in libgomp (PR libgomp/66005) Rainer Orth
2015-05-07 11:39 ` Jakub Jelinek
2015-05-07 18:07 ` Mike Stump
2015-05-08 8:40 ` Thomas Schwinge
2018-08-14 8:37 ` Martin Liška
2023-05-05 8:55 ` Support parallel testing in libgomp, part I [PR66005] Thomas Schwinge
2023-05-05 8:59 ` Support parallel testing in libgomp, part II [PR66005] Thomas Schwinge
2023-05-09 17:27 ` Bernhard Reutner-Fischer [this message]
2023-05-16 14:32 ` Support parallel testing in libgomp: fallback Perl 'flock' [PR66005] Thomas Schwinge
2023-05-06 14:15 ` Support parallel testing in libgomp, part I [PR66005] Bernhard Reutner-Fischer
2023-05-08 10:42 ` Thomas Schwinge
2023-05-08 17:52 ` Bernhard Reutner-Fischer
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=20230509192747.5bf23b93@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=mikestump@comcast.net \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=segher@kernel.crashing.org \
--cc=thomas@codesourcery.com \
--cc=tobias@codesourcery.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).