From: Stefan Weil <sw@weilnetz.de>
To: agraf@suse.de
Cc: gollub@b1-systems.de, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on xen_x86_64_debian_6_0
Date: Tue, 01 Nov 2011 08:36:46 +0100 [thread overview]
Message-ID: <4EAFA18E.1020502@weilnetz.de> (raw)
In-Reply-To: <20111101061932.15A7D3FC04@buildbot.b1-systems.de>
Am 01.11.2011 07:19, schrieb qemu@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder
> xen_x86_64_debian_6_0 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/xen_x86_64_debian_6_0/builds/78
>
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>
> Buildslave for this Build: yuzuki
>
> Build Reason: The Nightly scheduler named 'nightly_xen' triggered this
> build
> Build Source Stamp: [branch xen-next] HEAD
> Blamelist:
>
> BUILD FAILED: failed git
>
> sincerely,
> -The Buildbot
As far as I know from previous mails, the buildbots already do a retry
when git fails. The retry period used today is obviously too short.
We know that git fails rather often and that those failures take some
time. Is there any reason why a buildbot cannot retry until it
succeeds with a much larger time limit than today?
A git retry limit of several hours or even a day would not harm.
Mails from the buildbot are only useful if some user action is
required - when git fails, you can only wait.
Developers who want a fast feedback for their latest commits
can either poll the buildbot, or the buildbot must be configured
to send individual mails with more information.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-11-01 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 6:19 [Qemu-devel] buildbot failure in qemu on xen_x86_64_debian_6_0 qemu
2011-11-01 7:36 ` Stefan Weil [this message]
2011-11-01 8:07 ` Daniel Gollub
2011-11-01 10:21 ` Stefan Hajnoczi
2011-11-01 10:51 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2012-08-16 6:34 qemu
2012-08-11 6:47 qemu
2011-10-09 5:19 qemu
2011-10-04 5:03 qemu
2011-09-22 5:19 qemu
2011-09-05 5:09 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=4EAFA18E.1020502@weilnetz.de \
--to=sw@weilnetz.de \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.