public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/98678] 30_threads/future/members/poll.cc execution test FAILs
Date: Wed, 05 Apr 2023 16:51:50 +0000 [thread overview]
Message-ID: <bug-98678-4-Gb1vhfzXHw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98678
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danglin at gcc dot gnu.org
--- Comment #6 from John David Anglin <danglin at gcc dot gnu.org> ---
Fails consistently with timeout on hppa-unknown-linux-gnu. Increasing timeout
doesn't help.
dave@mx3210:~/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/testsuite$ time
./poll.exe
wait_for(0s): 10000098ns for 169420 calls, avg 59.0255ns per call
wait_until(system_clock minimum): 40000394ns for 169420 calls, avg 236.102ns
per call
wait_until(steady_clock minimum): 50000492ns for 169420 calls, avg 295.127ns
per call
wait_until(system_clock epoch): 1695216533549ns for 169420 calls, avg
1.0006e+07ns per call
wait_until(steady_clock epoch: 1694205876189ns for 169420 calls, avg 1e+07ns
per call
wait_for when ready: 0ns for 169420 calls, avg 0ns per call
/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/30_threads/future/members/poll.cc:129:
int main(): Assertion 'wait_for_0 < (ready * 30)' failed.
Aborted (core dumped)
real 56m29.632s
user 0m5.355s
sys 0m8.722s
next prev parent reply other threads:[~2023-04-05 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 12:16 [Bug libstdc++/98678] New: " ro at gcc dot gnu.org
2021-01-14 12:17 ` [Bug libstdc++/98678] " ro at gcc dot gnu.org
2021-01-14 12:59 ` redi at gcc dot gnu.org
2021-04-19 21:27 ` seurer at gcc dot gnu.org
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-07-28 7:05 ` rguenth at gcc dot gnu.org
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2023-04-05 16:51 ` danglin at gcc dot gnu.org [this message]
2023-05-29 10:03 ` jakub 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-98678-4-Gb1vhfzXHw@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).