You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2011/03/07 22:55:01 UTC
Re: Jenkins failure?
One additional piece of evidence:
The Job was set up at time X, and ran.
At time X plus a small delta, there's a job update by user "SYSTEM", where the
diff shows this:
--- /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_02-43-34/config.xml
+++ /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_05-16-06/config.xml
@@ -41,46 +41,50 @@
</hudson.triggers.SCMTrigger>
</triggers>
<concurrentBuild>false</concurrentBuild>
+ <rootModule>
+ <groupId>org.apache.uima</groupId>
+ <artifactId>uima-as</artifactId>
+ </rootModule>
<rootPOM>uima-as/pom.xml</rootPOM>
<goals>clean install -Pextended-test</goals>
<mavenName>Maven 3.0.2</mavenName>
The lines added look to be correct, but after this, we started getting this
failure report. I don't know what caused the user "SYSTEM" to add this. I
don't see any configuration for the rootModule in the Job setup.
-Marshall
On 3/7/2011 3:55 PM, Marshall Schor wrote:
> On 3/7/2011 2:30 PM, Niklas Gustavsson wrote:
>> On Mon, Mar 7, 2011 at 7:47 PM, Marshall Schor <ms...@schor.com> wrote:
>>> Any ideas, or should I just report this to the jenkins-users list?
>> I would report this to the Jenkins devs.
>>
> OK, done. -Marshall
>> /niklas
>>
>>
>
RE: Jenkins failure?
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Niklas,
Could you also restart the Lucene slave? I cannot do this through
webinterface (no admin rights). The machine is up and running; but the
message in the webinterface is unclear, Hudson should be able to start the
slave.
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Niklas Gustavsson [mailto:niklas@protocol7.com]
> Sent: Tuesday, March 08, 2011 9:51 PM
> To: builds@apache.org
> Subject: Re: Jenkins failure?
>
> On Tue, Mar 8, 2011 at 8:37 PM, Kristian Waagan
> <kr...@oracle.com> wrote:
> > I got the error again right now (after you restarted the slave) for
> > the Derby-trunk job, still on ubuntu1.
> > Saw it twice; one SCM triggered build and one manually started.
>
> Restarted again. No idea what causes this slave to behave like this.
>
> /niklas
Re: Jenkins failure?
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Tue, Mar 8, 2011 at 8:37 PM, Kristian Waagan
<kr...@oracle.com> wrote:
> I got the error again right now (after you restarted the slave) for the
> Derby-trunk job, still on ubuntu1.
> Saw it twice; one SCM triggered build and one manually started.
Restarted again. No idea what causes this slave to behave like this.
/niklas
Re: Jenkins failure?
Posted by Kristian Waagan <kr...@oracle.com>.
On 08.03.11 07:16, Niklas Gustavsson wrote:
> On Mon, Mar 7, 2011 at 10:55 PM, Marshall Schor<ms...@schor.com> wrote:
>> The lines added look to be correct, but after this, we started getting this
>> failure report. I don't know what caused the user "SYSTEM" to add this. I
>> don't see any configuration for the rootModule in the Job setup.
> SYSTEM is Jenkins itself. Looking into the code, it seems the root
> module is updated during the start of a build (while parsing the POM).
> In your case, the reason your seeing this diff is that the root module
> was updated on the first build.
>
> As for the problem, it seems to be happening for lots of builds right
> now, and all on the ubuntu1 slave as far as I can see. Perhaps
> something went wrong with this slave. I've restarted the slave and is
> now running some test builds on it.
I got the error again right now (after you restarted the slave) for the
Derby-trunk job, still on ubuntu1.
Saw it twice; one SCM triggered build and one manually started.
Regards,
--
Kristian
> /niklas
Re: Jenkins failure?
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Mar 7, 2011 at 10:55 PM, Marshall Schor <ms...@schor.com> wrote:
> The lines added look to be correct, but after this, we started getting this
> failure report. I don't know what caused the user "SYSTEM" to add this. I
> don't see any configuration for the rootModule in the Job setup.
SYSTEM is Jenkins itself. Looking into the code, it seems the root
module is updated during the start of a build (while parsing the POM).
In your case, the reason your seeing this diff is that the root module
was updated on the first build.
As for the problem, it seems to be happening for lots of builds right
now, and all on the ubuntu1 slave as far as I can see. Perhaps
something went wrong with this slave. I've restarted the slave and is
now running some test builds on it.
/niklas
Re: Jenkins failure?
Posted by Marshall Schor <ms...@schor.com>.
This morning I thought the only unusual thing might be that I delete the UIMA-AS
job and then made a new UIMA-AS job (with the same name).
So I just now did:
1) disabled the UIMA-AS job
2) made a new job, with the name UIMA-AS-2 (with the same configuration)
I kicked off a build of this, and it got beyond the failure point.
However there's a note on Builds that indicates a lot of people are having this
issue with their jobs, all running on Ubuntu1 - so an admin has "restarted"
Ubuntu1 - that might be the reason it's "going" now.
-Marshall
On 3/7/2011 5:58 PM, Marshall Schor wrote:
> just for testing, I tried the uimaj-sdk build - it still builds OK .
>
> -Marshall
>
> On 3/7/2011 5:35 PM, Marshall Schor wrote:
>> well, that shot in the dark still shows the same failure...
>>
>> -Marshall
>>
>> On 3/7/2011 5:33 PM, Marshall Schor wrote:
>>> I'm trying to get this to go, by reducing the diffs with the uimaj build. I
>>> added info that said to check out into "trunk" dir in the workspace, and also
>>> set a 50 minute time-out.
>>>
>>> I've queued another build - so we should know soon if this continues to fail.
>>>
>>> -Marshall
>>>
>>> On 3/7/2011 4:55 PM, Marshall Schor wrote:
>>>> One additional piece of evidence:
>>>>
>>>> The Job was set up at time X, and ran.
>>>>
>>>> At time X plus a small delta, there's a job update by user "SYSTEM", where the
>>>> diff shows this:
>>>>
>>>> --- /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_02-43-34/config.xml
>>>> +++ /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_05-16-06/config.xml
>>>> @@ -41,46 +41,50 @@
>>>> </hudson.triggers.SCMTrigger>
>>>> </triggers>
>>>> <concurrentBuild>false</concurrentBuild>
>>>> + <rootModule>
>>>> + <groupId>org.apache.uima</groupId>
>>>> + <artifactId>uima-as</artifactId>
>>>> + </rootModule>
>>>> <rootPOM>uima-as/pom.xml</rootPOM>
>>>> <goals>clean install -Pextended-test</goals>
>>>> <mavenName>Maven 3.0.2</mavenName>
>>>>
>>>> The lines added look to be correct, but after this, we started getting this
>>>> failure report. I don't know what caused the user "SYSTEM" to add this. I
>>>> don't see any configuration for the rootModule in the Job setup.
>>>>
>>>> -Marshall
>>>>
>>>> On 3/7/2011 3:55 PM, Marshall Schor wrote:
>>>>> On 3/7/2011 2:30 PM, Niklas Gustavsson wrote:
>>>>>> On Mon, Mar 7, 2011 at 7:47 PM, Marshall Schor <ms...@schor.com> wrote:
>>>>>>> Any ideas, or should I just report this to the jenkins-users list?
>>>>>> I would report this to the Jenkins devs.
>>>>>>
>>>>> OK, done. -Marshall
>>>>>> /niklas
>>>>>>
>>>>>>
>
Re: Jenkins failure?
Posted by Marshall Schor <ms...@schor.com>.
just for testing, I tried the uimaj-sdk build - it still builds OK .
-Marshall
On 3/7/2011 5:35 PM, Marshall Schor wrote:
> well, that shot in the dark still shows the same failure...
>
> -Marshall
>
> On 3/7/2011 5:33 PM, Marshall Schor wrote:
>> I'm trying to get this to go, by reducing the diffs with the uimaj build. I
>> added info that said to check out into "trunk" dir in the workspace, and also
>> set a 50 minute time-out.
>>
>> I've queued another build - so we should know soon if this continues to fail.
>>
>> -Marshall
>>
>> On 3/7/2011 4:55 PM, Marshall Schor wrote:
>>> One additional piece of evidence:
>>>
>>> The Job was set up at time X, and ran.
>>>
>>> At time X plus a small delta, there's a job update by user "SYSTEM", where the
>>> diff shows this:
>>>
>>> --- /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_02-43-34/config.xml
>>> +++ /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_05-16-06/config.xml
>>> @@ -41,46 +41,50 @@
>>> </hudson.triggers.SCMTrigger>
>>> </triggers>
>>> <concurrentBuild>false</concurrentBuild>
>>> + <rootModule>
>>> + <groupId>org.apache.uima</groupId>
>>> + <artifactId>uima-as</artifactId>
>>> + </rootModule>
>>> <rootPOM>uima-as/pom.xml</rootPOM>
>>> <goals>clean install -Pextended-test</goals>
>>> <mavenName>Maven 3.0.2</mavenName>
>>>
>>> The lines added look to be correct, but after this, we started getting this
>>> failure report. I don't know what caused the user "SYSTEM" to add this. I
>>> don't see any configuration for the rootModule in the Job setup.
>>>
>>> -Marshall
>>>
>>> On 3/7/2011 3:55 PM, Marshall Schor wrote:
>>>> On 3/7/2011 2:30 PM, Niklas Gustavsson wrote:
>>>>> On Mon, Mar 7, 2011 at 7:47 PM, Marshall Schor <ms...@schor.com> wrote:
>>>>>> Any ideas, or should I just report this to the jenkins-users list?
>>>>> I would report this to the Jenkins devs.
>>>>>
>>>> OK, done. -Marshall
>>>>> /niklas
>>>>>
>>>>>
>
Re: Jenkins failure?
Posted by Marshall Schor <ms...@schor.com>.
well, that shot in the dark still shows the same failure...
-Marshall
On 3/7/2011 5:33 PM, Marshall Schor wrote:
> I'm trying to get this to go, by reducing the diffs with the uimaj build. I
> added info that said to check out into "trunk" dir in the workspace, and also
> set a 50 minute time-out.
>
> I've queued another build - so we should know soon if this continues to fail.
>
> -Marshall
>
> On 3/7/2011 4:55 PM, Marshall Schor wrote:
>> One additional piece of evidence:
>>
>> The Job was set up at time X, and ran.
>>
>> At time X plus a small delta, there's a job update by user "SYSTEM", where the
>> diff shows this:
>>
>> --- /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_02-43-34/config.xml
>> +++ /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_05-16-06/config.xml
>> @@ -41,46 +41,50 @@
>> </hudson.triggers.SCMTrigger>
>> </triggers>
>> <concurrentBuild>false</concurrentBuild>
>> + <rootModule>
>> + <groupId>org.apache.uima</groupId>
>> + <artifactId>uima-as</artifactId>
>> + </rootModule>
>> <rootPOM>uima-as/pom.xml</rootPOM>
>> <goals>clean install -Pextended-test</goals>
>> <mavenName>Maven 3.0.2</mavenName>
>>
>> The lines added look to be correct, but after this, we started getting this
>> failure report. I don't know what caused the user "SYSTEM" to add this. I
>> don't see any configuration for the rootModule in the Job setup.
>>
>> -Marshall
>>
>> On 3/7/2011 3:55 PM, Marshall Schor wrote:
>>> On 3/7/2011 2:30 PM, Niklas Gustavsson wrote:
>>>> On Mon, Mar 7, 2011 at 7:47 PM, Marshall Schor <ms...@schor.com> wrote:
>>>>> Any ideas, or should I just report this to the jenkins-users list?
>>>> I would report this to the Jenkins devs.
>>>>
>>> OK, done. -Marshall
>>>> /niklas
>>>>
>>>>
>
Re: Jenkins failure?
Posted by Marshall Schor <ms...@schor.com>.
I'm trying to get this to go, by reducing the diffs with the uimaj build. I
added info that said to check out into "trunk" dir in the workspace, and also
set a 50 minute time-out.
I've queued another build - so we should know soon if this continues to fail.
-Marshall
On 3/7/2011 4:55 PM, Marshall Schor wrote:
> One additional piece of evidence:
>
> The Job was set up at time X, and ran.
>
> At time X plus a small delta, there's a job update by user "SYSTEM", where the
> diff shows this:
>
> --- /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_02-43-34/config.xml
> +++ /home/hudson/hudson/jobs/UIMA-AS/config-history/2011-03-05_05-16-06/config.xml
> @@ -41,46 +41,50 @@
> </hudson.triggers.SCMTrigger>
> </triggers>
> <concurrentBuild>false</concurrentBuild>
> + <rootModule>
> + <groupId>org.apache.uima</groupId>
> + <artifactId>uima-as</artifactId>
> + </rootModule>
> <rootPOM>uima-as/pom.xml</rootPOM>
> <goals>clean install -Pextended-test</goals>
> <mavenName>Maven 3.0.2</mavenName>
>
> The lines added look to be correct, but after this, we started getting this
> failure report. I don't know what caused the user "SYSTEM" to add this. I
> don't see any configuration for the rootModule in the Job setup.
>
> -Marshall
>
> On 3/7/2011 3:55 PM, Marshall Schor wrote:
>> On 3/7/2011 2:30 PM, Niklas Gustavsson wrote:
>>> On Mon, Mar 7, 2011 at 7:47 PM, Marshall Schor <ms...@schor.com> wrote:
>>>> Any ideas, or should I just report this to the jenkins-users list?
>>> I would report this to the Jenkins devs.
>>>
>> OK, done. -Marshall
>>> /niklas
>>>
>>>
>
Re: Jenkins failure?
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Mar 7, 2011 at 10:55 PM, Marshall Schor <ms...@schor.com> wrote:
> The lines added look to be correct, but after this, we started getting this
> failure report. I don't know what caused the user "SYSTEM" to add this. I
> don't see any configuration for the rootModule in the Job setup.
SYSTEM is Jenkins itself. Looking into the code, it seems the root
module is updated during the start of a build (while parsing the POM).
In your case, the reason your seeing this diff is that the root module
was updated on the first build.
As for the problem, it seems to be happening for lots of builds right
now, and all on the ubuntu1 slave as far as I can see. Perhaps
something went wrong with this slave. I've restarted the slave and is
now running some test builds on it.
/niklas