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 modula2/108344] Many tests time out: isatty called in a tight loop Date: Wed, 14 Jun 2023 12:36:59 +0000 [thread overview] Message-ID: <bug-108344-4-BL19IRLQeS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108344-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108344 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #6 from Rainer Orth <ro at gcc dot gnu.org> --- I hadn't seen those timeout for quite some time even before your patch (roughly since 20230123). So it seems whatever caused this is fixed (or at least masked).
next prev parent reply other threads:[~2023-06-14 12:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-09 15:12 [Bug modula2/108344] New: " ro at gcc dot gnu.org 2023-01-09 15:12 ` [Bug modula2/108344] " ro at gcc dot gnu.org 2023-01-13 13:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-05-16 14:52 ` cvs-commit at gcc dot gnu.org 2023-05-16 14:59 ` gaius at gcc dot gnu.org 2023-05-16 15:04 ` gaius at gcc dot gnu.org 2023-06-14 12:36 ` ro at gcc dot gnu.org [this message] 2023-07-28 21:51 ` 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-108344-4-BL19IRLQeS@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).