continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parashar-c, Jay" <Jay.Parasha...@airliquide.com>
Subject RE: Current prepare build queue never emptied
Date Mon, 28 Sep 2009 13:16:03 GMT
Not sure if it's related to this topic of builds getting stuck in build queue.  I have version
1.3.4 and have only one project(the default project is deleted and we have our own one). On
every build, the build shows the icon of "building" and the log says that projects are in
the build queue. I am unable to build any projects now (either through the scheduler or manually).
The "building" state remains for ever. The checking out phase happens successfully.

Is there a work around? This will be a great help if there is a way to build the project.
Currently, we are stuck.

Appreciate any help

Thanks
Jay



"2009-09-28 08:02:27,166 [pool-7-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Ending prepare build
2009-09-28 08:02:27,198 [pool-7-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action create-build-project-task
2009-09-28 08:02:27,198 [pool-7-thread-1] INFO  action#create-build-project-task  - Project
'LIBSnxtGen project' already being built.
2009-09-28 08:02:27,198 [pool-7-thread-1] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Projects are already in build queue."



-----Original Message-----
From: Martin Sudmann [mailto:martin.sudmann@priceminister.com] 
Sent: Monday, September 28, 2009 7:23 AM
To: users@continuum.apache.org
Subject: RE: Current prepare build queue never emptied

This happens also to freshly created projects. I think that the first
project after installation passed 3 times, using the DEFAULT_SCHEDULE with
the default build queue. Then I added 3 more build queues and clicked on the
build button for 2 projects rapidly one after the other; the first one got
stuck like I described in "current prepare build queue" and blocked the
second in "prepare build queue". I could delete the second one, but no way
to get rid of the first one in the "current" queue.
By the way, I have created the Jira
http://jira.codehaus.org/browse/CONTINUUM-2369.

Do you know where I can get a 1.3.3 or 1.3.2 war file from the download site
in order to test if this pb is specific to the new version? 
My old war file got corrupted.

Thanks,
Martin


-----Message d'origine-----
De : Brett Porter [mailto:brett@porterclan.net] De la part de Brett Porter
Envoyé : lundi 28 septembre 2009 01:20
À : users@continuum.apache.org
Objet : Re: Current prepare build queue never emptied

Does this happen on freshly created projects as well, or is only  
projects in a certain state? Do you have projects using other SCMs?

- Brett

On 24/09/2009, at 5:59 PM, Martin Sudmann wrote:

> The Bazaar commands are the following, the "tags" output comes from  
> the
> command "bzr log --verbose". But nothing has changed in our Bazaar
> configuration and the output of that command has always been like  
> that.
> When I restart tomcat, the queue is emptied, though the build button  
> on the
> project line on the project group page still shows "cancel build".
> When I try another build, it instantly gets stuck with the same log  
> entries
> as before.
>
>
> 2009-09-24 07:30:00,062 [pool-7-thread-1] INFO
> org.apache.continuum.scm.manager.Slf4jScmLogger  - EXECUTING: /bin/ 
> sh -c cd
> /users/integ.continue/apache-tomcat-6.0.18/webapps/con
> tinuum/data/working-directory/7 && bzr pull
> 2009-09-24 07:30:00,614 [pool-7-thread-1] INFO
> org.apache.continuum.scm.manager.Slf4jScmLogger  - EXECUTING: /bin/ 
> sh -c cd
> /users/integ.continue/apache-tomcat-6.0.18/webapps/con
> tinuum/data/working-directory/7 && bzr revno
> 2009-09-24 07:30:00,848 [pool-7-thread-1] INFO
> org.apache.continuum.scm.manager.Slf4jScmLogger  - EXECUTING: /bin/ 
> sh -c cd
> /users/integ.continue/apache-tomcat-6.0.18/webapps/con
> tinuum/data/working-directory/7 && bzr diff --revision 25547
> 2009-09-24 07:30:03,914 [pool-7-thread-1] INFO
> org.apache.continuum.scm.manager.Slf4jScmLogger  - EXECUTING: /bin/ 
> sh -c cd
> /users/integ.continue/apache-tomcat-6.0.18/webapps/con
> tinuum/data/working-directory/7 && bzr log --verbose
> 2009-09-24 07:30:39,339 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V50_0_1
> 2009-09-24 07:30:39,339 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V50_0_0
> 2009-09-24 07:31:44,008 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V49_0_0
> 2009-09-24 07:32:56,251 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V48_0_0
> 2009-09-24 07:32:56,261 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V47_0_1
> 2009-09-24 07:32:56,262 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V47_0_0
> 2009-09-24 07:35:06,347 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V46_0_1
> 2009-09-24 07:35:06,348 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V46_0_0
> 2009-09-24 07:35:06,364 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V45_0_1
> 2009-09-24 07:35:06,364 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V45_0_0
> 2009-09-24 07:35:06,364 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V42_0_0
> 2009-09-24 07:35:06,374 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V44_0_2
> 2009-09-24 07:35:06,376 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V44_0_1
> 2009-09-24 07:35:06,376 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V44_0_0
> 2009-09-24 07:38:42,451 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V43_0_2
> 2009-09-24 07:38:42,452 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V43_0_1
> 2009-09-24 07:38:42,453 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V43_0_0
> 2009-09-24 07:38:42,476 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> 2009-09-24 07:38:42,479 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V41_0_1
> 2009-09-24 07:38:42,481 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V41_0_0
> 2009-09-24 07:38:42,490 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V40_0_0
> 2009-09-24 07:38:42,500 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V39_0_0
> 2009-09-24 07:42:17,269 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V38_0_0
> 2009-09-24 07:42:17,271 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V37_0_0
> 2009-09-24 07:42:17,285 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V36_0_0
> 2009-09-24 07:42:17,288 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V35_0_0
> 2009-09-24 07:42:17,294 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V34_0_0
> 2009-09-24 07:42:17,296 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V33_0_0
> 2009-09-24 07:42:17,299 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V32_0_1
> 2009-09-24 07:42:17,300 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V32_0_0
> 2009-09-24 07:42:17,311 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V31_0_3
> 2009-09-24 07:42:17,311 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V31_0_2
> 2009-09-24 07:42:17,312 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V31_0_1
> 2009-09-24 07:42:17,312 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V31_0_0
> 2009-09-24 07:45:54,142 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> tags: V30_0_0
> 2009-09-24 07:45:54,143 [Thread-79] WARN
> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure  
> out of:
> :
>
>
> -----Message d'origine-----
> De : Brett Porter [mailto:brett@porterclan.net] De la part de Brett  
> Porter
> Envoyé : jeudi 24 septembre 2009 01:34
> À : users@continuum.apache.org
> Objet : Re: Current prepare build queue never emptied
>
> On 23/09/2009, at 7:57 PM, Martin Sudmann wrote:
>
>>
>> 2009-09-23 11:49:11,014 [http-9090-2] WARN
>> org.apache.struts2.components.Form  - No configuration found for the
>> specified action: 'none' in namespace: ''. Form action defaulting to
>> 'action' attribute's literal value.
>
> This could be a bug in the page that you should report, but I don't
> think it's the cause of the problem
>
>> I also get a lot of SCM warnings (don't know if this is related
>> though):
>>
>> 2009-09-23 11:40:53,695 [Thread-30] WARN
>> org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure
>> out of:
>> tags: V37_0_0
>
> The SCM problem seems the one relevant to your builds getting stuck.
> This is coming from the bazaar SCM provider that it doesn't understand
> the output line "tags: V37_0_0".
>
> It shouldn't block it though, so I'm not sure. Do the logs state what
> bzr command is being run?
>
> - Brett
>
>
>




Mime
View raw message