From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EDEDD385703C; Thu, 4 May 2023 13:02:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EDEDD385703C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683205322; bh=VjbBLpnxS+NnV0kcFPtSul1iC1w8ELroGLPdtWbQCW0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=K3D2yQ6sqiEHZPIH8k1TyitDFfeR7lR0nWOh2/Y9kAQn6KVDRoQCQ6vG9JWDceRvN 6tEti5Lpk1HJB3MY1hKbAFT4jvSEyXhsnud7smoc1gYbBOSfLAj0lE9jIstHkwjlW8 v8UFNGoTQYy1zqxqxdwsdhLwD3JulJjiad5FPvXA= From: "bergner at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98823 Peter Bergner 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 --- I just hit this twice yesterday (ie, infinite hang and no timeout) on our b= ig 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=3D64 worked for me.=