public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: buildbot users try branch builders for elfutils
Date: Thu, 28 Jul 2022 17:26:58 +0200	[thread overview]
Message-ID: <> (raw)


I setup git users try branches for elfutils. If you have commit
access to elfutils.git you can now push to a users/<name>/try-xxx
branch and the buildbot will do builds and sent you (the commit
author) email about the results. The builds are also visible at:

My workflow to use this looks like:

- git checkout -b ar_size
- hack, hack, hack... OK, looks good to submit
- git commit -a -m "Now who got an ar_size?"
- git push origin ar_size:users/mark/try-ar_size
- ... wait for the emails to come in or watch buildbot logs ...
- Send in patches and mention what the try bot reported
  (OK, I sent in the patch first, but you can reply to your
   original patch submission or in bugzilla what the try
   results were)

After your patches have been accepted you can delete the branch again:
- git push origin :users/mark/try-ar_size

Please use this only for patches you intend to submit and think are
ready but want to double check. Use the GCC Compile Farm machines if
you need to hack edit/compile/debug on a specific architecture.

But if you really need access to one of the buildbot machines for
investigating an issue, please contact

The try builders also upload logs to the bunsendb. And so are
visible here

See also the bunsen upload step in the try-build to get an URL
to the bunsen result for that specific build.

Please sent feedback (bad or good) to



             reply	other threads:[~2022-07-28 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 15:26 Mark Wielaard [this message]
2022-08-15  7:55 ` Martin Liška
2022-08-15 10:01   ` Mark Wielaard
2022-08-15 10:08     ` Martin Liška

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