public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "research_trasio at irq dot a4lg.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/29596] Parallel "make check-sim" is broken (unexpectedly passes without actually testing)
Date: Mon, 24 Oct 2022 06:32:50 +0000 [thread overview]
Message-ID: <bug-29596-4717-CaZL0gZt75@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29596-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29596
Tsukasa OI <research_trasio at irq dot a4lg.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tsukasa OI <research_trasio at irq dot a4lg.com> ---
Commit 86ef36f655d13cd39ff573de079b35a142f8cf42 is confirmed working. Closing
as resolved/fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-24 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 4:44 [Bug sim/29596] New: " research_trasio at irq dot a4lg.com
2022-09-22 4:46 ` [Bug sim/29596] " research_trasio at irq dot a4lg.com
2022-09-22 4:47 ` research_trasio at irq dot a4lg.com
2022-09-22 4:48 ` research_trasio at irq dot a4lg.com
2022-09-22 4:50 ` research_trasio at irq dot a4lg.com
2022-09-22 4:50 ` research_trasio at irq dot a4lg.com
2022-10-12 5:35 ` research_trasio at irq dot a4lg.com
2022-10-16 12:53 ` [Bug sim/29596] Parallel " research_trasio at irq dot a4lg.com
2022-10-16 13:00 ` research_trasio at irq dot a4lg.com
2022-10-23 20:22 ` vapier at gentoo dot org
2022-10-24 6:32 ` research_trasio at irq dot a4lg.com [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-29596-4717-CaZL0gZt75@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).