From: Mark Wielaard <mark@klomp.org>
To: Sam James <sam@gentoo.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] gcc_full_build_factory: call contrib/test_summary after make check
Date: Tue, 31 Jan 2023 22:01:02 +0100 [thread overview]
Message-ID: <20230131210102.GJ11361@gnu.wildebeest.org> (raw)
In-Reply-To: <20230131180432.562414-1-sam@gentoo.org>
On Tue, Jan 31, 2023 at 06:04:32PM +0000, Sam James wrote:
> This gives us a nice summary of the various dejagnu results.
Looks good.
Pushed,
Mark
prev parent reply other threads:[~2023-01-31 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:04 Sam James
2023-01-31 21:01 ` Mark Wielaard [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=20230131210102.GJ11361@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=sam@gentoo.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).