Waw .. So adding the txnmanager tests moved the duration from 13hrs to 22hrs?? (what is it, for 100+ tests) Or would anything else be causing this +9hrs of running time? This is something to look at closer I guess.
2010/11/3 Sim IJskes - QCG <s...@qcg.nl> > On 03-11-10 11:51, Jonathan Costers wrote: > >> Haven't seen these test failures before, ever, even when running the >> complete suite in situations with limited memory resources. This will >> require some investigation ... Did anything change recently to the build >> environment (hardware, OS, JVM, ...)? >> > > hudson was upgraded recently. > > > You can check the diagnostics output in the build output on Hudson (all >> way >> at the end for now), the order in which it is executed doesn't really >> matter >> IMO. But indeed, if executing it first, its output will come first :-). >> > > Indeed, i hoped it would show the memory settings. Not. :-) > > > It is great to see the txnmanager tests pass, though! >> > > Yes! We are a project with an impressive QA run, takes 22 hours now to > complete. > > Gr. Sim > > > -- > QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl > Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397 >
