public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/98680] New: Several 30_threads tests are flaky
Date: Thu, 14 Jan 2021 12:33:12 +0000 [thread overview]
Message-ID: <bug-98680-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98680
Bug ID: 98680
Summary: Several 30_threads tests are flaky
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: i386-pc-solaris2.11, sparc-sun-solaris2.11,
i686-apple-darwin*, x86_64-apple-darwin*,
hppa2.0w-hp-hpux11.11
Several 30_threads tests are flaky on Solaris, more often on Solaris/x86 but
also on SPARC:
For the last couple of days, the counts are like this:
11 30_threads/barrier/arrive_and_wait.cc execution test
11 30_threads/barrier/arrive_and_wait.cc execution test program timed out.
1 30_threads/barrier/arrive.cc execution test
1 30_threads/barrier/arrive.cc execution test program timed out.
20 30_threads/barrier/completion.cc execution test
20 30_threads/barrier/completion.cc execution test program timed out.
14 30_threads/latch/3.cc execution test
14 30_threads/latch/3.cc execution test program timed out.
1 30_threads/semaphore/try_acquire_for.cc execution test
1 30_threads/semaphore/try_acquire_for.cc execution test program timed
out.
5 30_threads/semaphore/try_acquire_until.cc execution test
5 30_threads/semaphore/try_acquire_until.cc execution test program timed
out.
At least Darwin and HP-UX are likewise affected; I haven't looked closer for
possible others.
As an example, I ran arrive_and_wait.exe for ca. 100 times with the following
timing:
93 real 0.01
1 real 0.73
1 real 0.95
1 real 1.03
1 real 1:13.00
next reply other threads:[~2021-01-14 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 12:33 ro at gcc dot gnu.org [this message]
2021-01-14 12:33 ` [Bug libstdc++/98680] " ro at gcc dot gnu.org
2021-01-14 13:02 ` redi at gcc dot gnu.org
2021-01-14 13:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-04-27 13:05 ` redi at gcc dot gnu.org
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=bug-98680-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).