public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Indu Bhagat <indu.bhagat@oracle.com>,
	binutils@sourceware.org,  buildbot@sourceware.org
Subject: Re: libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks)
Date: Fri, 23 Dec 2022 17:13:02 +0100	[thread overview]
Message-ID: <0805c9d4e7dc82c514e72947a419f6f29e276b13.camel@klomp.org> (raw)
In-Reply-To: <ba4b0899-03d0-9d24-b905-2a8dcc00563e@oracle.com>

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 
> if there are enough resources for users to be doing this so frequently 
> (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 
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

      reply	other threads:[~2022-12-23 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221222225457.1095930-1-indu.bhagat@oracle.com>
2022-12-23 14:22 ` Mark Wielaard
2022-12-23 14:41   ` Frank Ch. Eigler
2022-12-23 16:06     ` Mark Wielaard
2022-12-23 15:24   ` Indu Bhagat
2022-12-23 16:13     ` Mark Wielaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0805c9d4e7dc82c514e72947a419f6f29e276b13.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=buildbot@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).