qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, gollub@b1-systems.de,
	qemu@buildbot.b1-systems.de, agraf@suse.de,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_openbsd_4.9
Date: Tue, 4 Oct 2011 07:45:28 +0100	[thread overview]
Message-ID: <20111004064528.GA7766@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4E8A3DD8.8050800@codemonkey.ws>

On Mon, Oct 03, 2011 at 05:57:28PM -0500, Anthony Liguori wrote:
> On 10/03/2011 06:15 PM, qemu@buildbot.b1-systems.de wrote:
> >The Buildbot has detected a new failure on builder default_openbsd_4.9 while building qemu.
> >Full details are available at:
> >  http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/44
> >
> >Buildbot URL: http://buildbot.b1-systems.de/qemu/
> >
> >Buildslave for this Build: kraxel_openbsd49
> >
> >Build Reason: The Nightly scheduler named 'nightly_default' triggered this build
> >Build Source Stamp: [branch master] HEAD
> >Blamelist:
> >
> >BUILD FAILED: failed git
> 
> Is there a way to suppress buildbot failures when the failed stage
> is git?  Not a huge deal but seems like a potential improvement.

We've discussed adding custom Python configuration code to ignore these
failures.

Looking at the buildbot documentation there is a 'retry' parameter for
version control which "specifies a tuple of (delay, repeats) which means
that when a full VC checkout fails, it should be retried up to repeats
times, waiting delay seconds between attempts".  This sounds like it
could work.

I suggest setting retry = (5 * 60, 3) so that we wait 5 minutes after a
failed git fetch and try 3 times.

Daniel: In the buildbot 0.8.3p1-1 docs I found the 'retry' parameter
under 4.11.3 Source Checkout.  Is it possible to add this parameter?

Thanks,
Stefan

  reply	other threads:[~2011-10-04  7:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 23:15 [Qemu-devel] buildbot failure in qemu on default_openbsd_4.9 qemu
2011-10-03 22:57 ` Anthony Liguori
2011-10-04  6:45   ` Stefan Hajnoczi [this message]
2011-10-04  8:12     ` Daniel Gollub
2011-10-04 10:02       ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2013-01-12 22:12 qemu
2012-12-13 10:28 qemu
2012-11-02  0:07 qemu
2012-08-15 23:07 qemu
2012-08-03 23:08 qemu
2012-07-28 23:07 qemu
2012-07-19 23:16 qemu
2012-07-17 23:06 qemu
2012-06-08 23:43 qemu
2012-05-22 23:07 qemu
2012-03-03  0:39 qemu
2012-02-04  0:07 qemu
2011-11-12  0:27 qemu
2011-09-30 23:06 qemu
2011-09-20 23:05 qemu
2011-09-21  7:45 ` Alexander Graf
2011-09-21  8:27 ` Kevin Wolf
2011-09-21  8:29   ` Brad
2011-09-21  8:50     ` Kevin Wolf
2011-09-22  6:45       ` Daniel Gollub
2011-10-10 14:23   ` Gerd Hoffmann
2011-10-10 15:35     ` Daniel Gollub
2011-10-10 16:37       ` Kevin Wolf
2011-08-21 20:36 qemu

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=20111004064528.GA7766@stefanha-thinkpad.localdomain \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@buildbot.b1-systems.de \
    /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 NNTP newsgroup(s).