Re: Build restarts itself, killing the log?

Given that you seem to be deleting directories looking that the cleanup
seems like a good avenue to pursue.  Good luck!

Jtf


INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
-      [exec] At D:\CruiseControl\scripts\cleanup_nightlytag.ps1:38 char:24

INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
-      [exec] +                     $out = remove-item  <<<< $DIR -force
-recurse

2009/10/18 Paul Müller-Salget <[email protected]>

>  Hi,
>
>
>
> I am quite sure, that there is no second process running and we are using
> only one worker.
>
>
>
> Furthermore I see the log is written in case of a build failed, so I guess
> it has to be 2): it was deleted.
>
>
>
> I guess I will have to take a look into what is happening in the cleanup
> target. Perhaps there is a wrong path variable or something like that…
>
>
>
> Thanks for the help, I’ll keep you posted if it turns out to be a real
> CruiseControl issue.
>
>
>
> Regards
>
> Paul
>
>
>
> *From:* Jeffrey Fredrick [mailto:[email protected]]
> *Sent:* Mittwoch, 14. Oktober 2009 02:10
> *To:* [email protected]
> *Subject:* Re: [Cruisecontrol-user] Build restarts itself, killing the
> log?
>
>
>
>
>
> Hi Paul,
>
>
>
> A good guess, but that's not quite what's happening.  The build attempt
> takes place in a try {} block with a finally{} that sets the status to IDLE,
> and then the catch is outside of that.
>
>
>
> So what is happening is the builder finishes the build but then throws an
> exception because the Ant log file it is looking or isn't there.  Two
> possible reasons for that:
>
>
>
>   1) it was never written
>
>   2) it was deleted
>
>
>
> Is it possible you have other builds running at the same time?  Or do you
> have only one worker thread?
>
>
>
> Jtf
>
>
>
> 2009/10/13 Paul Müller-Salget <[email protected]>
>
> Hi all,
>
>
>
> I have a strange CruiseControl issue:
>
>
>
> Every night we run a special build target, that builds a tag that was done
> automatically.
>
>
>
> This target needs ~90 minutes to complete.
>
>
>
> Since some days, I only get logs if the build fails, but not if it
> succeeded.
>
>
>
> The *Wrapper log* shows the following:
>
>
>
> INFO   | jvm 4    | 2009/10/12 23:56:54 | [cc]Oct-12 23:56:54 ScriptRunner
> -    [testng]   at org.testng.TestNG.main(TestNG.java:874)
>
> INFO   | jvm 4    | 2009/10/12 23:56:55 | [cc]Oct-12 23:56:55 ScriptRunner
> -      [echo] Finished 20091012 run at 2356
>
> INFO   | jvm 4    | 2009/10/12 23:56:55 | [cc]Oct-12 23:56:55 ScriptRunner
> -      [echo] [cleanup]
>
> INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
> -      [exec] Remove-Item : The specified path, file name, or both are too
> long. The fully qu
>
> INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
> -      [exec] alified file name must be less than 260 characters, and the
> directory name must
>
> INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
> -      [exec]  be less than 248 characters.
>
> INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
> -      [exec] At D:\CruiseControl\scripts\cleanup_nightlytag.ps1:38 char:24
>
> INFO   | jvm 4    | 2009/10/12 23:57:12 | [cc]Oct-12 23:57:11 ScriptRunner
> -      [exec] +                     $out = remove-item  <<<< $DIR -force
> -recurse
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 | [cc]Oct-12 23:59:44 Project
> - Project HEAD_night_tag_permwin04:  idle
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 | [cc]Oct-12 23:59:44
> jectController- HEAD_night_tag_permwin04 Controller: build progress event:
> idle
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 | [cc]Oct-12 23:59:44 Project
> - exception attempting build in project HEAD_night_tag_permwin04
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |
> net.sourceforge.cruisecontrol.CruiseControlException: ant logfile
> D:\CruiseControl\.\log.xml does not exist.
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.builders.AntBuilder.getAntLogAsElement(AntBuilder.java:444)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.builders.AntBuilder.build(AntBuilder.java:227)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.Schedule.build(Schedule.java:169)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.Project.build(Project.java:226)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.Project.execute(Project.java:147)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.ProjectConfig.execute(ProjectConfig.java:402)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> net.sourceforge.cruisecontrol.ProjectWrapper.run(ProjectWrapper.java:69)
>
> INFO   | jvm 4    | 2009/10/12 23:59:44 |               at
> java.lang.Thread.run(Thread.java:619)
>
>
>
> I read this like:
>
> At 23:57:12 the build was almost done and doing the cleanup (never mind the
> error message there, it can be ignored).
>
> Than at 23:59:44 the build went idle and was restarted, effectively killing
> the still running build and its logfile?
>
>  ...
>

-- 
CITCON
Continuous Integration and Testing Conference
http://www.citconf.com/

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user