On Wed, 25 Apr 2007, Curt Arnold <[EMAIL PROTECTED]> wrote: > Current run in progress did not have logging-log4j-component in its > workspace despite the metadata looking okay.
Maybe this happened because I removed the directories in mid-run. vmgump is taking more than nine hours for a single Gump run ATM. > Hopefully these tiny little projects are taking up much disk space > on vmgump. I didn't know that it was near its limits. Hope it > didn't cause problems. It is at its limits and svn is to blame for some part of it (a svn working copy takes so much more disk space than a CVS one). Looking at it from the ressource consumption POV we can be glad that we don't try to build Cocoon ATM. Getting something with a bigger disk and more power is on our infrastructure wish list ... Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
