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 19FE73858417 for ; Wed, 2 Nov 2022 11:49:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 19FE73858417 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 tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id D26383061FA4; Wed, 2 Nov 2022 12:49:10 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id AF379413CD0E; Wed, 2 Nov 2022 12:49:09 +0100 (CET) Message-ID: Subject: Re: Testing patches before push to trunk From: Mark Wielaard To: Indu Bhagat , binutils@sourceware.org Date: Wed, 02 Nov 2022 12:49:09 +0100 In-Reply-To: <531f662f-f994-405d-7560-9b022041e382@oracle.com> References: <531f662f-f994-405d-7560-9b022041e382@oracle.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-3033.1 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 List-Id: Hi Indu, On Wed, 2022-11-02 at 00:05 -0700, Indu Bhagat via Binutils wrote: > Is there a way I can test the patch series on a wider set of=20 > platforms/environments and weed out the issues before the patch set > is integrated ? binutils has a try bot on https://builder.sourceware.org/ If you push a try- branch to your users branch the buildbot will pick it up and run a build on a bunch of different architectures. https://builder.sourceware.org/buildbot/#/builders?tags=3Dbinutils-try The remote branch should be called users/username/try-something. So assuming your local branch with the patches to test is called "frob", you can push it to a users try- branch like: - git push origin frob:users/ibhagat/try-frob Then wait for the emails to come in or watch the logs at the above URL. Note that not all arches are green at the moment, so you need to check if a failure is because of your new code or was already existing. Cheers, Mark