public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/98823] go testsuite and timeouts
Date: Thu, 04 May 2023 13:02:01 +0000 [thread overview]
Message-ID: <bug-98823-4-8l8saBmjHe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98823-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2023-05-04
CC| |bergner at gcc dot gnu.org,
| |boger at gcc dot gnu.org
--- Comment #17 from Peter Bergner <bergner at gcc dot gnu.org> ---
I just hit this twice yesterday (ie, infinite hang and no timeout) on our big
internal P10 development system. Talking with Lynn Boger who is our golang
lead, she mentioned hitting this too on big systems with lots of cores. She
had opened an upstream golang issue discussing it:
https://github.com/golang/go/issues/47246
Lynn's workaround of setting GOMAXPROCS=64 worked for me.
prev parent reply other threads:[~2023-05-04 13:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 15:29 [Bug go/98823] New: " jakub at gcc dot gnu.org
2021-01-25 18:55 ` [Bug go/98823] " ian at airs dot com
2021-01-25 19:09 ` schwab@linux-m68k.org
2021-01-25 19:34 ` ian at airs dot com
2021-01-25 19:41 ` schwab@linux-m68k.org
2021-01-25 19:44 ` schwab@linux-m68k.org
2021-01-25 20:13 ` ian at airs dot com
2021-01-25 20:52 ` schwab@linux-m68k.org
2021-01-25 20:59 ` ian at airs dot com
2021-01-25 23:31 ` jakub at gcc dot gnu.org
2021-02-01 14:15 ` jakub at gcc dot gnu.org
2021-02-07 17:48 ` ian at airs dot com
2021-02-07 18:09 ` ian at airs dot com
2021-02-07 19:00 ` jakub at gcc dot gnu.org
2021-02-12 17:25 ` ian at airs dot com
2021-04-22 12:03 ` jakub at gcc dot gnu.org
2021-04-22 12:46 ` redi at gcc dot gnu.org
2023-05-04 13:02 ` bergner at gcc dot gnu.org [this message]
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-98823-4-8l8saBmjHe@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).