public inbox for libstdc++-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 r12-3596] libstdc++: Increase timeout factor for slow pb_ds tests Date: Thu, 16 Sep 2021 22:07:25 +0000 (GMT) [thread overview] Message-ID: <20210916220725.8A2D93857001@sourceware.org> (raw) https://gcc.gnu.org/g:433789330609c571983a4e1f5c3e0caf3d7a6178 commit r12-3596-g433789330609c571983a4e1f5c3e0caf3d7a6178 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Sep 16 20:10:02 2021 +0100 libstdc++: Increase timeout factor for slow pb_ds tests Compiling these tests still times out too often when running the testsuite with more parallel jobs than there are available cores. Signed-off-by: Jonathan Wakely <jwakely@redhat.com> libstdc++-v3/ChangeLog: * testsuite/ext/pb_ds/regression/tree_map_rand.cc: Increase timeout factor to 3. * testsuite/ext/pb_ds/regression/tree_set_rand.cc: Likewise. Diff: --- libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc | 2 +- libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc b/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc index 8ff6e926003..62904749ee7 100644 --- a/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc +++ b/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc @@ -4,7 +4,7 @@ // { dg-require-cstdint "" } // This can take long on simulators, timing out the test. // { dg-options "-DITERATIONS=5" { target simulator } } -// { dg-timeout-factor 2.0 } +// { dg-timeout-factor 3.0 } // -*- C++ -*- diff --git a/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc b/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc index af7f7ffde22..16a864e0e30 100644 --- a/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc +++ b/libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc @@ -4,7 +4,7 @@ // { dg-require-cstdint "" } // This can take long on simulators, timing out the test. // { dg-options "-DITERATIONS=5" { target simulator } } -// { dg-timeout-factor 2.0 } +// { dg-timeout-factor 3.0 } // -*- C++ -*-
reply other threads:[~2021-09-16 22:07 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=20210916220725.8A2D93857001@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: linkBe 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).