From: Mark Wielaard <mark@klomp.org>
To: libabigail@sourceware.org
Cc: buildbot@sourceware.org
Subject: buildbot users try branch builders for libabigail
Date: Wed, 20 Jul 2022 01:35:26 +0200 [thread overview]
Message-ID: <Ytc/vloB6KjYCFJC@wildebeest.org> (raw)
Hi,
I setup git users try branches for libabigail. If you have commit
access to libabigail.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:
https://builder.sourceware.org/buildbot/#/builders?tags=libabigail-try
My workflow to use this (if I had libabigail commit access) looks
like:
- git checkout -b pr29346
- hack, hack, hack... OK, looks good to submit
- git commit -a -m "The ultimate PR29346 fix"
- git push origin pr29346:users/mark/try-pr29346
- ... wait for the emails to come in or watch buildbot logs ...
- Send in patches and mention what the try bot reported
After your patches have been accepted you can delete the branch again:
- git push origin :users/mark/try-pr29346
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.
https://cfarm.tetaneutral.net/
But if you really need access to one of the buildbot machines for
investigating an issue, please contact buildbot@sourceware.org.
The try builders also upload logs to the bunsendb. And so are
visible here https://builder.sourceware.org/testruns/
Please sent feedback (bad or good) to buildbot@sourceware.org
Cheers,
Mark
next reply other threads:[~2022-07-19 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 23:35 Mark Wielaard [this message]
2022-07-20 9:50 ` Dodji Seketeli
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=Ytc/vloB6KjYCFJC@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=libabigail@sourceware.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).