|
We have a test setup now, but it needs some more investigation regarding some tests failing against some test databases. We leave this issue open for now and move it into the next release. The job exists: http://hudson.qa.jboss.com/hudson/view/Hibernate%20Community/job/hibernate-search-trunk/ Sorry, the above URL is not the public-facing Hudson. Please, check this one: Looks great. There seems to be a few database setups which seem to fail due to wrong user credentials or drivers. If we cannot fix them we should remove them from the setup. Here are the ones which look suspicious:
I am not quite sure why postgresql824 and postgresql837 are not working. Could be that one test is not properly ending a transaction and the whole thing stands still until the job gets killed/times out. Either way, I think after fixing/removing db2v91 and mssql2008 we can resolve this issue. The next step is to make the tests pass on all these environments. Looking at some of the tests reports a lot of problems seems to be just test setup related. I added the credentials to DB2 v9.1. It should work fine now. The problem with MS SQL 2008 was that it was using an old version of the driver. I updated both MS SQL 2005 and MS SQL 2008 to use the 2.0 version of the driver (as we use for DB certification in EAP side). Regarding the jobs which are "grey" (aborted): it's probably a transaction hanging somewhere. It may be related to a problem we discussed some time ago, involving threads + integer vars to count finished threads (instead of AtomicInteger) + improper handing of exceptions. I'll check that as part of another JIRA. If you spot any failure which may indicate a test setup problem, let me know. It should not have any problem now, as it just runs maven with the following command: $ mvn clean install -P$database,jdbc-drivers,with-optional-jars -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Assigning this to Juca who can hopefully set something up in our Hudson environment. The ability to run against different databases is provided via profiles now in the POM. We basically just need a SQLServer profile for example.
It would be great to get some notifications as well, in case the build fails.