Re: derbynetmats/DerbyNet/derbynetmats/testij fails

[Satheesh Bandaram]

Thanks for raising test failure issues. I do agree test failures should be addressed quickly. I also want to suggest some ways to make sure a failure is not caused by your own changes... Feel free to add any other suggestions you or others may have. With so many changes going into derby, some small number of failures are bound to happen. I believe Tomohito's changes also got delayed because of test failures, not related to his changes. Check the nightly reports (http://incubator.apache.org/derby/derby_tests.html) If you see same failure there, it is probably not caused by you. Still suggest alerting derby-dev, so someone would address them. Run the test with and without your changes. Most offen if the test fails the same way, it might not be your problem. I am sure there are more tricks out there... Satheesh Bernt M. Johnsen wrote: I still can't get derbyall to run (I've been away for a week): Now it's derbynetmats/DerbyNet/derbynetmats/testij that fails. See http://www.multinet.no/~solberg/public/Apache/Derby/testlog/Linux-2.4.20-31.9_i686-i686/180348-derbynetmats_diff.txt I seriously believe that we need to stabilize Derby in a way that ensures that can run derbyall to verify that I have not introduced any problems with my own work.