Hi, I am trying to figure out why the Search DB2 test in Jenkins is still failing - http://hudson.qa.jboss.com/hudson/job/hibernate-search-master-dbmatrix-coreSnapshot/database=db2-97,jdk=java16_default,label=hibernate/
When I run the test locally against Core 4.0.0-SNAPSHOT using the DB2 profile defined in the Search pom the test passes and I can see that the change in the DB2Dialect (which should fix the issue) gets picked up. In QA the Search build also depends on a Core SNAPSHOT, but the test keeps failing. Am I missing something? --Hardy On Nov 29, 2011, at 7:04 PM, Hardy Ferentschik wrote: > Hi, > > in the test fixing mood I am right now, I pushed several fixes. It starting > to look good. > There are two remaining issues one against DB2 (HSEARCH-992) and one against > Sybase. > > The DB2 one is an interesting one. The test entity defines an UUID field with > no further mapping configuration. This gets translated on DB2 into the column > 'uuid char(255)' where char is nor a valid type. I am actually lost where > exactly the mapping from UUID to a certain column type occurs. Maybe someone > can enlighten me. > > Not sure about the Sybase errors. It keeps dumping out: > > 12:05:02,448 (main) WARN SqlExceptionHelper:143 - SQL Error: 7738, SQLState: > null > 12:05:02,449 (main) ERROR SqlExceptionHelper:144 - Message empty. > > Has anyone seen this before? > > Last but not least, there is SQLServer. I think the tests should work. There > are two servers the test are running against - mssql2008R1 and mssql2008R2. > Against the former the build completes successfully. Against the latter the > build gets killed after 3 hours. Looking at the existing builds it seems it > has always done that. It might be the database doesn't feel that well :-) > Maybe someone with access to this db could have a look and maybe restart it. > > --Hardy > > > On Nov 29, 2011, at 11:07 AM, Strong Liu wrote: > >> >> >> On Nov 29, 2011, at 6:03 PM, Sanne Grinovero wrote: >> >>> On 29 November 2011 04:15, Strong Liu <st...@hibernate.org> wrote: >>>> cool >>>> but I don't see where you change the Core version to snapshot in this job >>>> configuration….. >>> >>> It's just a property we pass to Maven to override the one defined in >>> the root pom: >>> >>> -DhibernateVersion=4.0.0-SNAPSHOT >> >> oh, okay, I didn't check there :) >> >>> >>> I uploaded a fresh snapshot version of Core, is that being done >>> automatically by the Hibernate Core jobs or could we have them doing >>> that? >> >> yes, hibernate-core-master deploys snapshot everyday >> >>> >>> Sanne >> >> _______________________________________________ >> 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 _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev