public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97944] 30_threads/jthread/95989.cc fails randomly Date: Tue, 24 Nov 2020 23:41:56 +0000 [thread overview] Message-ID: <bug-97944-4-4ce8s3289D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97944-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97944 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:a3313a2214a6253672ab4fa37a2dcf57fd0f8dce commit r11-5326-ga3313a2214a6253672ab4fa37a2dcf57fd0f8dce Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 24 23:22:01 2020 +0000 libstdc++: Disable failing tests [PR 97936] These tests are unstable and causing failures due to timeouts. Disable them until the cause can be found, so that testing doesn't have to wait for them to timeout. libstdc++-v3/ChangeLog: PR libstdc++/97936 PR libstdc++/97944 * testsuite/29_atomics/atomic_integral/wait_notify.cc: Disable. Do not require pthreads, but add -pthread when appropriate. * testsuite/30_threads/jthread/95989.cc: Likewise. * testsuite/30_threads/latch/3.cc: Likewise. * testsuite/30_threads/semaphore/try_acquire_until.cc: Likewise.
next prev parent reply other threads:[~2020-11-24 23:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-23 10:41 [Bug libstdc++/97944] New: " clyon at gcc dot gnu.org 2020-11-23 11:16 ` [Bug libstdc++/97944] " redi at gcc dot gnu.org 2020-11-23 12:38 ` clyon at gcc dot gnu.org 2020-11-24 22:29 ` redi at gcc dot gnu.org 2020-11-24 22:41 ` clyon at gcc dot gnu.org 2020-11-24 22:48 ` seurer at gcc dot gnu.org 2020-11-24 23:17 ` redi at gcc dot gnu.org 2020-11-24 23:41 ` cvs-commit at gcc dot gnu.org [this message] 2020-11-24 23:46 ` redi at gcc dot gnu.org 2020-11-26 10:40 ` redi at gcc dot gnu.org 2021-04-19 10:40 ` redi at gcc dot gnu.org 2022-06-14 19:27 ` cvs-commit 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-97944-4-4ce8s3289D@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: 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).