public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r10-10561] libstdc++: Increase timeout for pthread7-rope.cc test
Date: Tue, 26 Apr 2022 13:11:54 +0000 (GMT)	[thread overview]
Message-ID: <20220426131154.C45333858406@sourceware.org> (raw)

https://gcc.gnu.org/g:4c91bfc5f9b64310b437797eae97d7602745e409

commit r10-10561-g4c91bfc5f9b64310b437797eae97d7602745e409
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 6 11:10:31 2022 +0000

    libstdc++: Increase timeout for pthread7-rope.cc test
    
    This test spawns thousands of threads and so times out if the tests are
    run with a low timeout value and the machine is busy.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/ext/rope/pthread7-rope.cc: Add dg-timeout-factor.
    
    (cherry picked from commit e19e2989c36c5148ceb67a1f2575718fc1927ce6)

Diff:
---
 libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc b/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
index 4896053a013..1d0e9a96cae 100644
--- a/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
+++ b/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
@@ -20,6 +20,7 @@
 // { dg-do run }
 // { dg-options "-pthread"  }
 // { dg-require-effective-target pthread }
+// { dg-timeout-factor 2 }
 
 #include <ext/rope>
 #include <cstring>
@@ -33,7 +34,7 @@ typedef __gnu_cxx::rope<char, std::allocator<char> > rope_type;
 rope_type foo2;
 rope_type foo4;
 
-void* thread_main(void *) 
+void* thread_main(void *)
 {
   // To see a problem with gcc 3.3 and before, set a break point here.
   // Single step through c_str implementation, call sched_yield after


                 reply	other threads:[~2022-04-26 13:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220426131154.C45333858406@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.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).