From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id B7E6D3858C51; Mon, 20 Jun 2022 10:48:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B7E6D3858C51 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x09.wildebeest.org [172.31.17.139]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 7905330006B1; Mon, 20 Jun 2022 12:48:04 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 1EA8F2E81645; Mon, 20 Jun 2022 12:48:04 +0200 (CEST) Date: Mon, 20 Jun 2022 12:48:04 +0200 From: Mark Wielaard To: binutils@sourceware.org, gdb@sourceware.org Cc: buildbot@sourceware.org, Thomas Fitzsimmons , fche@redhat.com Subject: buildbot users try branch builders Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2022 10:48:07 -0000 Hi, As an experiment we now have try builders for binutils and gdb. If you have commit access to binutils-gdb.git you can now push to your users//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=binutils-try https://builder.sourceware.org/buildbot/#/builders?tags=gdb-try My workflow to use this looks like: - git checkout -b frob - hack, hack, hack... OK, looks good to submit - git commit -a -m "Awesome hack" - git push origin frob:users/mark/try-frob - ... 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-frob 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 buildbot@sourceware.org. The armhf and arm64 builders have left out for now since they are a bit too slow. We'll hopefully get a 8 core Ampare machine from the Oregon State University this week so we can also enable those arm builders. Tom, I haven't hooked up the debian-ppc64 builder yet. It would take another ~3GB disk space for the new try builders. Frank, the try builders also upload logs to the bunsendb. And so are visible here https://builder.sourceware.org/testruns/ I think this is useful, but maybe these try logs are just noise? Please sent feedback (bad or good) to buildbot@sourceware.org Currently this is only for the binutils and gdb projects, but if this looks useful and when we get some new hardware we can roll it out to other sourceware projects. Cheers, Mark