I know the cause. I am in the midst of large changes in the test suite infrastructure. Hopefully the complete change will be checked in today, which will fix these failures
-----Original Message----- From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 12, 2006 5:03 AM To: Max Andersen Cc: Steve Ebersole; hibernate-dev@lists.jboss.org Subject: Re: [hibernate-dev] [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors] You could reproduce the problem by: svn co http://anonhibernate.labs.jboss.com/trunk/Hibernate3 cd Hibernate3 sh build.sh junitreport The result is the same as by cruisecontrol and I cannot see any other trace. You could also inspect the changes between revision 10954 and 10963 to see what have caused the problem. Max Rydahl Andersen wrote: > > yes I see the following in the logs: > > > /home/cruisecontrol/work/checkout/hibernate-db-matrix/build.xml:254: > The following error occurred while executing this line: > /home/cruisecontrol/work/checkout/hibernate-db-matrix/build.xml:278: > java.lang.NullPointerException > > Any idea on how i can get the full stacktrace ? :) > /max > > >> Any latter fail. See them from the left tab. Builds fail before even >> tests do begin. It's the same for the other databases too. You could >> navigate to them from http://cruisecontrol.jboss.com. >> >> Max Rydahl Andersen wrote: >> >>> >>> Could you give me a link to the failing testcase ? >>> >>> looking the link you send i don't see it failing there ? >>> >>> /max >>> >>>> Hi Again. I haven't received confirmation about the sql server tests >>>> from you. At the moment hibernate tests fail due to some changes not >>>> related to sqlserver so I send you a reference to the last good build: >>>> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds- testsuite?log=log20061207220047 >>>> >>>> >>>> >>>> Here is my last message again. >>>> ---------------------------------------------------- >>>> Hi. As you see I used jtds driver for this one. It doesn't support >>>> setting the transaction isolation level to snapshot, but I tunned the >>>> database this way: >>>> ALTER DATABASE cruisecontrol SET ALLOW_SNAPSHOT_ISOLATION ON; >>>> ALTER DATABASE cruisecontrol SET READ_COMMITTED_SNAPSHOT ON; >>>> >>>> This should set the default isolation level to snapshot. >>>> >>>> When I ran the tests with the MS jdbc driver I got one more error >>>> than with the jdts driver. It is >>>> org.hibernate.test.legacy.MasterDetailTest.testCachedCollectionRefresh. >>>> >>>> But I'm not sure in the results as the cruisecontrol builds give half >>>> the errors of these I've got from the mentioned tests. >>>> >>>> So to conclude see if you see the results consistent with your local >>>> tests. I'll modify the build if you do not like the jtds driver or >>>> something else. >>>> >>>> >>>> _______________________________________________ >>>> hibernate-dev mailing list >>>> hibernate-dev@lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>> >>> >>> >>> >>> > > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
