public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] Fix builder step name.
Date: Thu, 16 Jun 2022 23:35:04 +0200	[thread overview]
Message-ID: <YquiCHZk29em2i2k@wildebeest.org> (raw)
In-Reply-To: <af4c5c04-d392-4b1d-b68f-8b5af58f141d@suse.cz>

Hi Martin,

On Thu, Jun 16, 2022 at 07:08:49AM +0200, Martin Liška wrote:
> Change builder step like:
> make -k checkCC_FOR_TARGET=clang CXX_FOR_TARGET=cl
> 
> to
> make -k check CC_FOR_TARGET=clang CXX_FOR_TARGET=cl

Looks good to me. Please push.

Thanks,

Mark

> ---
>  builder/master.cfg | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/builder/master.cfg b/builder/master.cfg
> index 8455dfe..e49b2fa 100644
> --- a/builder/master.cfg
> +++ b/builder/master.cfg
> @@ -1638,7 +1638,7 @@ def binutils_gdb_factory_factory(runtestflags=None):
>                  make_check_command.append('RUNTESTFLAGS='+runtestflags)
>          binutils_gdb_factory.addStep(steps.Test(
>                  command=make_check_command,
> -                name=('make -k check' + (runtestflags if runtestflags else ''))[:50], # length limit
> +                name=('make -k check' + (' ' + runtestflags if runtestflags else ''))[:50], # length limit
>                  timeout=14400, # 4 hours should be enough to get some output
>                  haltOnFailure=False, flunkOnFailure=False))  # test failure = ok
>          binutils_gdb_factory.addStep(steps.ShellCommand(
> -- 
> 2.36.1
> 

      reply	other threads:[~2022-06-16 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  5:08 Martin Liška
2022-06-16 21:35 ` 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=YquiCHZk29em2i2k@wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=mliska@suse.cz \
    /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).