From: Sam James <sam@gentoo.org>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH 2/2] gcc_full_build_factory: call contrib/test_summary after make check
Date: Tue, 31 Jan 2023 17:34:51 +0000 [thread overview]
Message-ID: <420BC6E8-C088-4AD3-96C3-969AC884DE00@gentoo.org> (raw)
In-Reply-To: <20230131093117.GH11361@gnu.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
> On 31 Jan 2023, at 09:31, Mark Wielaard <mark@klomp.org> wrote:
>
> On Tue, Jan 31, 2023 at 01:56:11AM +0000, Sam James wrote:
>> This gives us a nice summary of the various dejagnu results.
>
> Looks like a nice idea in general.
>
> But it also renames the *.sum files to .sum.sent, which means
> they next bunsen step will fail to fetch them. You need to add
> -t: prevents logs from being renamed
>
Oh, good spot! Let me fix.
> Also the "wrapper" text about emailing the sums is a little
> odd imho. But it looks like there is no way to suppress that.
>
I want to add an option for that as it's a bit confusing when we run
It in our Gentoo packaging too. We'll circle back to that.
Best,
sam
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2023-01-31 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 1:56 [PATCH 1/2] gcc_full_build_factory: pass '-k' to make check to maximise results Sam James
2023-01-31 1:56 ` [PATCH 2/2] gcc_full_build_factory: call contrib/test_summary after make check Sam James
2023-01-31 9:31 ` Mark Wielaard
2023-01-31 17:34 ` Sam James [this message]
2023-01-31 9:27 ` [PATCH 1/2] gcc_full_build_factory: pass '-k' to make check to maximise results Mark Wielaard
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=420BC6E8-C088-4AD3-96C3-969AC884DE00@gentoo.org \
--to=sam@gentoo.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.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).