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 789993858D1E; Fri, 23 Dec 2022 16:13:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 789993858D1E 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 64D413000340; Fri, 23 Dec 2022 17:13:03 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 2C0F5413CD0E; Fri, 23 Dec 2022 17:13:03 +0100 (CET) Message-ID: <0805c9d4e7dc82c514e72947a419f6f29e276b13.camel@klomp.org> Subject: Re: libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks) From: Mark Wielaard To: Indu Bhagat , binutils@sourceware.org, buildbot@sourceware.org Date: Fri, 23 Dec 2022 17:13:02 +0100 In-Reply-To: References: <20221222225457.1095930-1-indu.bhagat@oracle.com> <98617b373993a3c6054b9389cddfde56b9aec7d1.camel@klomp.org> 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=-3032.5 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 Fri, 2022-12-23 at 07:24 -0800, Indu Bhagat wrote: > heh, binutils-try buildbot's enthusiastic user I am, yes. I did > wonder=20 > if there are enough resources for users to be doing this so frequently= =20 > (with almost every patch set before commit), I hope its not a problem ? It isn't a problem, a binutils build/check takes just a couple of minutes and at least for the x86_64 and i386 builders there are more than one worker. The most resource constrained one is the s390x worker, but it is still able to catch up. Worst case you have to wait an hour till your job is finally scheduled. You can always check whether there are a lot of pending jobs at=20 https://builder.sourceware.org/buildbot/#/pendingbuildrequests (There are often a couple which take multiple hours but are only ran a few times a day) Cheers, Mark