7 del < ...running last checks via final.sql 7 add > ...timed out trying to kill all testers, > skipping last scripts (if any). NOTE: the > likely cause of the problem killing testers is > probably not enough VM memory OR test cases that > run for very long periods of time (so testers do not > have a chance to notice stop() requests
Just for a sanity check, I ran stress.multi on an idle machine (I wasn't doing builds or anything else at the time), and this time it passed. So I think my machine was just overloaded and the test timed out. I don't think it's the same as what you're looking at.
David
Sunitha Kambhampati wrote:
David Van Couvering wrote:
It built fine and passed all the JDBC api tests, except for stress.multi, which I think is a problem with my machine and not your source...
Which stress.multi test failed.. was it the encrypted test run ? The reason I ask is I am looking into the encrypted stress.multi failure (Derby241) and wondering if this failure is similar to that one. If you still have the testrun output, can you post some details on it ie - the derby.log , the database etc.
Thanks, Sunitha.
