public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: Testing patches before push to trunk
Date: Wed, 02 Nov 2022 12:49:09 +0100	[thread overview]
Message-ID: <d36a36198edeb1e71a671040f1c948b365cec84a.camel@klomp.org> (raw)
In-Reply-To: <531f662f-f994-405d-7560-9b022041e382@oracle.com>

Hi Indu,

On Wed, 2022-11-02 at 00:05 -0700, Indu Bhagat via Binutils wrote:
> Is there a way I can test the patch series on a wider set of 
> platforms/environments and weed out the issues before the patch set
> is integrated ?

binutils has a try bot on https://builder.sourceware.org/

If you push a try- branch to your users branch the buildbot will pick
it up and run a build on a bunch of different architectures.

https://builder.sourceware.org/buildbot/#/builders?tags=binutils-try

The remote branch should be called users/username/try-something.
So assuming your local branch with the patches to test is called
"frob", you can push it to a users try- branch like:

- git push origin frob:users/ibhagat/try-frob

Then wait for the emails to come in or watch the logs at the above URL.

Note that not all arches are green at the moment, so you need to check
if a failure is because of your new code or was already existing.

Cheers,

Mark

  reply	other threads:[~2022-11-02 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  7:05 Indu Bhagat
2022-11-02 11:49 ` Mark Wielaard [this message]
2022-11-03  1:39   ` Hans-Peter Nilsson
2022-11-02 11:53 ` Nick Clifton

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=d36a36198edeb1e71a671040f1c948b365cec84a.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    /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).