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 1FAE83858D1E; Tue, 19 Jul 2022 23:35:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1FAE83858D1E 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 (213-10-231-91.fixed.kpn.net [213.10.231.91]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id EBFB1300047C; Wed, 20 Jul 2022 01:35:26 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 93C802E819FF; Wed, 20 Jul 2022 01:35:26 +0200 (CEST) Date: Wed, 20 Jul 2022 01:35:26 +0200 From: Mark Wielaard To: libabigail@sourceware.org Cc: buildbot@sourceware.org Subject: buildbot users try branch builders for libabigail Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP 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: Tue, 19 Jul 2022 23:35:30 -0000 Hi, I setup git users try branches for libabigail. If you have commit access to libabigail.git you can now push to a 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=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