Setup hudson job testing Search against several databases

Description

Bug got introduced during refactoring of DocumentBuilder. Since we are not testing against SQLServer or any other db where the generated SQL could be a problem the error passed through.
the fix is quite easy, but it is harder to write a unit test. Maybe we should try to get a proper Hudson setup instead running against multiple databases.

Activity

Show:

Juraci Paixão Kröhling April 2, 2010 at 2:53 PM

Marking as resolved, as we have quite a few jobs in Hudson for CI, including for Search.

Emmanuel Bernard April 2, 2010 at 2:34 PM

What's the status of this Juca?

Sanne Grinovero April 1, 2010 at 6:07 PM

so can this be closed now?

Juraci Paixão Kröhling November 6, 2009 at 12:13 PM

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

Hardy Ferentschik November 6, 2009 at 11:40 AM

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:

  • db2v91

  • mssql2008

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.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created March 6, 2009 at 7:33 PM
Updated July 1, 2010 at 12:37 PM
Resolved April 2, 2010 at 2:53 PM