public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Sam James <>
Subject: Re: [PATCH 1/2] gcc_full_build_factory: pass '-k' to make check to maximise results
Date: Tue, 31 Jan 2023 10:27:44 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Sam,

On Tue, Jan 31, 2023 at 01:56:10AM +0000, Sam James wrote:
> We want to keep going even if we hit failures for a maximally useful
> log and set of results.

Yes, that makes sense for the full build.



      parent reply	other threads:[~2023-01-31  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  1:56 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
2023-01-31  9:27 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).