| Summary: | EntityMappings*testsuite and Multitenant testsuite failed on Sybase during INT to VARCHAR conversion | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Praba Vijayaratnam <prabaharan.vijayaratnam> |
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.orm-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sabine.heider, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | sybase | ||
|
Description
Praba Vijayaratnam
on 2011-11-23 trunk build, following tests failed for same cause: org.eclipse.persistence.testing.tests.jpa.jpql.JUnitJPQLComplexTestSuite.caseTypeTest org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsAdvancedJUnitTestCase.testSetup org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsAdvancedJUnitTestCase.test*Employee org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsAdvancedJUnitTestCase.testUnidirectional* org.eclipse.persistence.testing.tests.jpa.xml.inherited.EntityMappingsInheritedJUnitTestCase.test*BeerConsumer org.eclipse.persistence.testing.tests.jpa.xml.advanced.compositepk.AdvancedCompositePKJunitTest.testDepartmentAdmin org.eclipse.persistence.testing.tests.jpa.xml.advanced.AdvancedJunitTest.testGF1894 org.eclipse.persistence.testing.tests.jpa.xml.composite.advanced.EntityMappingsAdvancedJUnitTestCase.testSetup org.eclipse.persistence.testing.tests.jpa.xml.composite.advanced.EntityMappingsAdvancedJUnitTestCase.test*Employee See the following bugs: bug 406193, bug 407156, bug 407285. The patches are available with version 2.6.0 and fix the test issues - org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsMultitenantJUnitTestCase.* - org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsAdvancedJUnitTestCase.testMockDynamicClassCRUD - org.eclipse.persistence.testing.tests.jpa.jpql.JUnitJPQLComplexTestSuite.caseTypeTest I have seen the remaining issues that you mentioned in Comment 1 as well in an experimental test run that I performed with the database parameter DYNAMIC_PREPARE=false being set. With DYNAMIC_PREPARE=true (which is also the default setting afaik) those errors were not present. I haven't investigated those issues any further yet, though. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |