On Sun, 2014-09-21 at 02:37 -0500, Norbert Thiebaud wrote:
On Sun, Sep 21, 2014 at 4:20 AM, David Ostrovsky <d.ostrovsky@gmx.de> wrote:
On Sun, 2014-09-21 at 00:26 -0500, Norbert Thiebaud wrote:
I've disabled the gerrit buildbot. It seems there is a problem with
starting Windows build
but since the problem occured with mutiple tb at the same time, it
must be more that just one tb acting up.
in the mean time that problem caused spamming of the irc and the logs
due to the same build being started over and over...
From looking in the logs [1] of affected change [2] i cannot see any
misbehavior from builbdbt side. It looks like, TB39 cannot fetch the
change for some reasons and reports status "canceled" back, in which
case buildbot re-initialize the task in the queue, and the same TB39
(probably in wedged state?) 60 sec later picks the task again and we
have a loop.
Yeah but tb42 (also a windows) was doing the same thing...
so I think this is more than just one box acting up...
This sounds like tb script on windows is broken?
I'll try to reproduce locally, in the mean time it does no good to
have the thing spamming.
We don't have any Linux tb for Gerrit üatch set verifications atm and
thus we cannot perform verifications on all supported platform anyway.
So may be just revoke all Windows TBs the right to pick up changes and
still let buildbot enabled? Working verifications on Mac OS X is better
then no verifications at all. Let's face it: that's the current
situation.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.