Last thing in log is this: INFO:gump:Document run using [<gump.document.forrest.ForrestDocumenter instance at 0x99df2f4>]
i.e. running forrest. That said, I can see no reason, why waiting for soemthing to run might cause this Gumpy to grow. That said, I hate how I coded the 'tear down' code in Python, it was (is) a mega kludge since Python doesn't seem mature enough for process management at that level. BTW: I ran forrest by hand for grins. validate-xdocs: /data3/gump/forrest/src/documentation/content/xdocs/xml-forrest/work/build_x ml-forrest_xml-forrest-scratchpad-forrestdoc-ws.xml:1:1: Premature end of file. BUILD FAILED /home/ajack/opt/forrest/forrest.build.xml:761: Could not validate document /data3/gump/forrest/src/documentation/content/xdocs/xml-forrest/work/build_x ml-forrest_xml-forrest-scratchpad-forrestdoc-ws.xml Now, that didn't take long, so Gumpy ought have moved on. With --debug we'll see if it did (and if the problems were in nagging, or RSS, or ... ???) [I've not added anything new recently, that ought be there, or ought be running other than in unit tests.] BTW: We saw this error when we were low on disk space. Maybe it is a stray file that wasn't cleaned up, but it seems odd it showed up again. I'll delete it and see what gives next run. regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
