You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by bu...@apache.org on 2014/11/25 15:07:47 UTC
buildbot failure in ASF Buildbot on forrest-trunk
The Buildbot has detected a new failure on builder forrest-trunk while building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/forrest-trunk/builds/17
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: lares_ubuntu
Build Reason: The AnyBranchScheduler scheduler named 'on-forrest-commit' triggered this build
Build Source Stamp: [branch forrest/trunk] 1641622
Blamelist: sjur
BUILD FAILED: failed
Sincerely,
-The Buildbot
Re: buildbot failure in ASF Buildbot on forrest-trunk
Posted by Sjur Moshagen <sj...@mac.com>.
26. nov. 2014 kl. 05:08 skrev David Crossley <cr...@apache.org>:
>
> On Tue, Nov 25, 2014 at 10:45:26PM +0100, Sjur Moshagen wrote:
>> 25. nov. 2014 kl. 22:33 skrev David Crossley <cr...@apache.org>:
>>> I had a similar problem back on September 14. See the logs above.
>>> The next day it came good all by itself.
>>
>> Thanks for the follow-up. I am kind of hoping that it will disappear by itself also this time, we’ll see tomorrow.
>
> I just triggered it with another commit, and now it is happy.
> No idea why.
Strange - good that it is happy, anyway.
And thanks for adding my change to the status.xml file - should have remembered that.
Sjur
Re: buildbot failure in ASF Buildbot on forrest-trunk
Posted by David Crossley <cr...@apache.org>.
On Tue, Nov 25, 2014 at 10:45:26PM +0100, Sjur Moshagen wrote:
> 25. nov. 2014 kl. 22:33 skrev David Crossley <cr...@apache.org>:
> >
> > On Tue, Nov 25, 2014 at 03:18:39PM +0100, Sjur Moshagen wrote:
> >>> program finished with exit code 0
> >>> elapsedTime=0.017328
> >>> program finished with exit code 1
> >>> program finished with exit code 0
> >>
> >> The process before (svn --version) ends with a normal exit code, and the same for the following process. That is, one single, anonymous process did not end successfully, but everything else did.
> >>
> >> How come?
> >
> > I do not know either. Something about "corrupted xml".
> >
> > I had a similar problem back on September 14. See the logs above.
> > The next day it came good all by itself.
>
> Thanks for the follow-up. I am kind of hoping that it will disappear by itself also this time, we’ll see tomorrow.
I just triggered it with another commit, and now it is happy.
No idea why.
-David
> > If not, then perhaps need to contact Infrastructure.
> > I am not sure how, but start here:
> > http://ci.apache.org/#buildbot
>
> Ok.
>
> Sjur
>
Re: buildbot failure in ASF Buildbot on forrest-trunk
Posted by Sjur Moshagen <sj...@mac.com>.
25. nov. 2014 kl. 22:33 skrev David Crossley <cr...@apache.org>:
>
> On Tue, Nov 25, 2014 at 03:18:39PM +0100, Sjur Moshagen wrote:
>>> program finished with exit code 0
>>> elapsedTime=0.017328
>>> program finished with exit code 1
>>> program finished with exit code 0
>>
>> The process before (svn --version) ends with a normal exit code, and the same for the following process. That is, one single, anonymous process did not end successfully, but everything else did.
>>
>> How come?
>
> I do not know either. Something about "corrupted xml".
>
> I had a similar problem back on September 14. See the logs above.
> The next day it came good all by itself.
Thanks for the follow-up. I am kind of hoping that it will disappear by itself also this time, we’ll see tomorrow.
> If not, then perhaps need to contact Infrastructure.
> I am not sure how, but start here:
> http://ci.apache.org/#buildbot
Ok.
Sjur
Re: buildbot failure in ASF Buildbot on forrest-trunk
Posted by David Crossley <cr...@apache.org>.
On Tue, Nov 25, 2014 at 03:18:39PM +0100, Sjur Moshagen wrote:
> 25. nov. 2014 kl. 15:07 skrev buildbot@apache.org:
> >
> > The Buildbot has detected a new failure on builder forrest-trunk while building ASF Buildbot. Full details are available at:
> > http://ci.apache.org/builders/forrest-trunk/builds/17
> >
> > Buildbot URL: http://ci.apache.org/
> >
> > Buildslave for this Build: lares_ubuntu
> >
> > Build Reason: The AnyBranchScheduler scheduler named 'on-forrest-commit' triggered this build
> > Build Source Stamp: [branch forrest/trunk] 1641622
> > Blamelist: sjur
> >
> > BUILD FAILED: failed
> >
> > Sincerely,
> > -The Buildbot
>
> Thank you, Buildbot!
>
> Except that I do not understand what has gone wrong. In the log file for the failed process, the only fail is logged as follows:
>
> > program finished with exit code 0
> > elapsedTime=0.017328
> > program finished with exit code 1
> > program finished with exit code 0
>
> The process before (svn --version) ends with a normal exit code, and the same for the following process. That is, one single, anonymous process did not end successfully, but everything else did.
>
> How come?
I do not know either. Something about "corrupted xml".
I had a similar problem back on September 14. See the logs above.
The next day it came good all by itself.
If not, then perhaps need to contact Infrastructure.
I am not sure how, but start here:
http://ci.apache.org/#buildbot
-David
> Sjur
>
Re: buildbot failure in ASF Buildbot on forrest-trunk
Posted by Sjur Moshagen <sj...@mac.com>.
25. nov. 2014 kl. 15:07 skrev buildbot@apache.org:
>
> The Buildbot has detected a new failure on builder forrest-trunk while building ASF Buildbot. Full details are available at:
> http://ci.apache.org/builders/forrest-trunk/builds/17
>
> Buildbot URL: http://ci.apache.org/
>
> Buildslave for this Build: lares_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named 'on-forrest-commit' triggered this build
> Build Source Stamp: [branch forrest/trunk] 1641622
> Blamelist: sjur
>
> BUILD FAILED: failed
>
> Sincerely,
> -The Buildbot
Thank you, Buildbot!
Except that I do not understand what has gone wrong. In the log file for the failed process, the only fail is logged as follows:
> program finished with exit code 0
> elapsedTime=0.017328
> program finished with exit code 1
> program finished with exit code 0
The process before (svn --version) ends with a normal exit code, and the same for the following process. That is, one single, anonymous process did not end successfully, but everything else did.
How come?
Sjur