From continuum-users-return-4571-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Thu Sep 06 13:49:36 2007 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 30655 invoked from network); 6 Sep 2007 13:49:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Sep 2007 13:49:35 -0000 Received: (qmail 3458 invoked by uid 500); 6 Sep 2007 13:49:28 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 3436 invoked by uid 500); 6 Sep 2007 13:49:28 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 3424 invoked by uid 99); 6 Sep 2007 13:49:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2007 06:49:27 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2007 13:50:43 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1ITHjC-0004Oy-JN for continuum-users@maven.apache.org; Thu, 06 Sep 2007 06:49:02 -0700 Message-ID: <12522974.post@talk.nabble.com> Date: Thu, 6 Sep 2007 06:49:02 -0700 (PDT) From: Anshula To: continuum-users@maven.apache.org Subject: Re: Scheduled Builds Timing out In-Reply-To: <46DF9EA3.2030902@venisse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: anshula.bhat@isobar.net References: <12499048.post@talk.nabble.com> <46DEC3FB.4060600@venisse.net> <12499984.post@talk.nabble.com> <46DEC78E.7090507@venisse.net> <12500482.post@talk.nabble.com> <46DEF98E.9040708@venisse.net> <12509142.post@talk.nabble.com> <46DF9EA3.2030902@venisse.net> X-Virus-Checked: Checked by ClamAV on apache.org I dont think so. When I installed Continuum, I followed the standard installation instructions. I havent changed the logging configurations anywhere. These logs are for 1 day only. Continuum is running as a service and I have scheduled a build at 7:30 pm. Usually what I observe is that the logs get written at 7:30 pm when Continuum starts to checkout source and build the files. I am attaching one more file from a previo http://www.nabble.com/file/p12522974/wrapper.20070829.log wrapper.20070829.log us day as well, which has logs of some forced builds a= s well. Thanks Anshula Emmanuel Venisse wrote: >=20 > Do you have redefined log levels? I don't see lot of logs in the file you > sent. >=20 > Anshula a =C3=A9crit : >> Emmanuel, >>=20 >> In the build-output-directory of each project as well as on the build >> result >> page, the last build that I can find is the last successful build.=20 >> The Builds that have a timeout, did not generate a build result. >> The only place that it logged about the timeout was the Continuum log >> file/Wrapper.log. >> Should it have generated a build result ? Coz it did not get built at >> all... >>=20 >> Thanks, >> Anshula >>=20 >>=20 >> Emmanuel Venisse wrote: >>> In build result page, choose a build result with timeout ant take the >>> build id, then go to the build-output-directory and send us the content >>> of >>> the build output you'll find in this directory. >>> >>> Emmanuel >>> >>> Anshula a =C3=A9crit : >>>> Hi Emmanuel, >>>> >>>> The File is as attached. Thanks for the help. >>>> >>>> Anshula >>>> >>>> >>>> Emmanuel Venisse wrote: >>>>> Can you send your logs? >>>>> >>>>> Anshula a =C3=A9crit : >>>>>> Hi Emmanuel, >>>>>> >>>>>> Acutally right now I am just building, there are no unit tests added >>>>>> as >>>>>> of >>>>>> now. The build does not take more than 1-2 minutes, I tried building >>>>>> all >>>>>> projects locally and verified this.=20 >>>>>> >>>>>> Regards, >>>>>> Anshula >>>>>> >>>>>> >>>>>> Emmanuel Venisse wrote: >>>>>>> Maybe you have a test that hang out? >>>>>>> >>>>>>> Emmanuel >>>>>>> >>>>>>> Anshula a =C3=A9crit : >>>>>>>> Hello all, >>>>>>>> >>>>>>>> I am using Continuum 1.1-beta-2 with Perforce to integrate all my >>>>>>>> projects >>>>>>>> in the build management system. >>>>>>>> I have been using it over a month or so, and have around 15 projec= t >>>>>>>> groups/projects integrated into it. I have scheduled a build in th= e >>>>>>>> system >>>>>>>> which runs at 7:30 pm everyday. >>>>>>>> The build system has been running properly building when it detect= s >>>>>>>> changes >>>>>>>> at the scheduled time >>>>>>>> >>>>>>>> But since 2 days, everyday the builds are timing out. I have set a >>>>>>>> Maximum >>>>>>>> job execution time of 3600 secs. Each of the projects does not tak= e >>>>>>>> more >>>>>>>> than 1 minute to build.=20 >>>>>>>> >>>>>>>> Continuum queues all the projects and prints a warning in the log >>>>>>>> file >>>>>>>> like >>>>>>>> - >>>>>>>> "Task >>>>>>>> org.apache.maven.continuum.buildqueue.BuildProjectTask@151179a >>>>>>>> didn't >>>>>>>> complete within time, cancelling it." And shows all the projects i= n >>>>>>>> queued >>>>>>>> state only. I need to restart Continuum to build them again. >>>>>>>> >>>>>>>> Thanks for your time. Any help will be appreciated. >>>>>>>> Regards, >>>>>>>> Anshula >>>>> >>>> http://www.nabble.com/file/p12500482/wrapper.20070901.log >>>> wrapper.20070901.log=20 >>> >>> >>=20 >=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/Scheduled-Builds-Timing= -out-tf4384387.html#a12522974 Sent from the Continuum - Users mailing list archive at Nabble.com.