Not sure if this is related but i've been digging through the ccnet logs and have found that the builds we are having problems with are writing out "standard-output stream closed -- null received in event" followed by "standard-output stream closed -- null received in event" then followed by "process exited event received" when running their Mercurial source block.
Last week we had a problem with Mercurial not correctly parsing the history log which we are still trying to resolve(thread here: http://groups.google.com/group/ccnet-user/browse_thread/thread/dfb35a744c9e5612/c2aab3ae439c506b?lnk=gst&q=mercurial#c2aab3ae439c506b ). Could this problem be in some way related? Jim On Aug 10, 3:22 pm, jim_offroadcode <[email protected]> wrote: > For the record.... We also have a project which is apparently building > successfully but is being reported as Failure. > > On Aug 10, 3:16 pm, jim_offroadcode <[email protected]> > wrote: > > > Thanks for the reply Benjamin. I noticed the site at build.nauck-it.de > > is also showing similar symptoms for two of their builds (the > > FastForward.Net and NauckIT.Nant builds) although i've no idea if this > > is related in any way. > > > Hoping someone has a solution for this! > > > On Aug 10, 3:09 pm, Benjamin Baumann <[email protected]> wrote: > > > > I had similar problems when the error occured in Publishers. When it > > > happens, the cctray status is success, the project trigger with a success > > > condition are triggered but the dashboard and mail status are failed. > > > > I did not fix this yet. > > > > 2010/8/10 jim_offroadcode <[email protected]> > > > > > We've been having some issues with CCnet 1.5.7256.1 recently where > > > > some builds are running and failing but being reported as Successful > > > > builds. The build logs show the exception/failure status but the > > > > dashboard is still displaying green ticks and Success. > > > > > Obviously this is a concern as failed builds are going unnoticed. > > > > > Has anyone else had this problem? > >
