Hi, 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: https://builder.sourceware.org/buildbot/#/builders?tags=elfutils-try
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. https://cfarm.tetaneutral.net/ But if you really need access to one of the buildbot machines for investigating an issue, please contact build...@sourceware.org. The try builders also upload logs to the bunsendb. And so are visible here https://builder.sourceware.org/testruns/ 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 build...@sourceware.org Cheers, Mark
