Sasvata Chatterjee wrote: > > After more debug, it turned out that there were two types of problems. > One was that .xtest, .xlog, etc files were not being copied into the > target/test-classes directory, which were fixed with additional resource > elements. Also, there were some delay(...) calls in the test code that > were on the hairy edge, at least on my env. So far all the tests are > running, when run on a project by project basis. > > Tests still seem erratic when invoked from a multiproject build. I > think the memory usage grows, page-faults grow and things start taking > longer to "way longer". All tests that depend on certain timeouts, like > event/thread tests, start failing. > Yes, this was my assumption for our problems as well - it seems to me that m2 has a memory leak. With a fresh checkout of Cocoon we need to run m2 several times before it can build the whole project (we have lots of subprojects).
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
