Re: [hibernate-dev] hibernate-documentation CI job
by default hudson archives artifacts generated by maven. So you have access to them. For example http://hudson.jboss.org/hudson/job/hibernate-documentation/4/org.hibernate$hibernate-manual/artifact/org.hibernate/hibernate-manual/3.3.0-SNAPSHOT/hibernate-manual-3.3.0-SNAPSHOT.war Max Rydahl Andersen wrote, On 04/30/2008 11:23 PM (EEST): For the daily ones, i don't see a benefit to deploy them somewhere. For releases we will handle that. Will they be viewable via hudson ? -max Max, the eclipse documentation stuff we discussed is the only thing of which I can think which may potentially benefit from deploying these documentation daily snapshots. Do you see a benefit/need? Not at the current point in time. -max On Apr 29, 2008, at 4:00 AM, Aleksandar Kostadinov wrote: Hallo, This mail is to announce the newly created hibernate-documentation job. It is now setup to run daily. Let me know if you want artifacts deployed on some repository as now it doesn't deploy anywhere. Thanks, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate-documentation CI job
Max Rydahl Andersen wrote, On 04/29/2008 12:08 PM (EEST): link ? internal: http://hudson.qa.jboss.com/hudson/view/hibernate/job/hibernate-documentation/ public: http://hudson.jboss.org/hudson/job/hibernate-documentation/ /max Hallo, This mail is to announce the newly created hibernate-documentation job. It is now setup to run daily. Let me know if you want artifacts deployed on some repository as now it doesn't deploy anywhere. Thanks, Aleksandar ___ 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] hibernate-documentation CI job
Hallo, This mail is to announce the newly created hibernate-documentation job. It is now setup to run daily. Let me know if you want artifacts deployed on some repository as now it doesn't deploy anywhere. Thanks, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] building hibernate trunk
I see what the error is. It is trying to run po2xml but the file doesn't
exist. So I installed kdesdk package on RHEL4 and get the following error:
[INFO] [jdocbook:translate {execution: default}]
[INFO] Processing translation [es-ES]
the translation of 'yes' doesn't start with a tag.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] there was a problem executing command; check output
[INFO]
[INFO] Trace
org.jboss.jdocbook.i18n.actions.process.ExecutionException: there was a
problem executing command; check output
at
org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:70)
at
org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:45)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.generateTranslatedXML(TranslateXmlAction.java:107)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:66)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:80)
at
org.jboss.jdocbook.i18n.actions.TranslateXmlAction.perform(TranslateXmlAction.java:50)
at
org.jboss.maven.plugins.jdocbook.TranslationMojo.doExecute(TranslationMojo.java:38)
at
org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:272)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Is there any plan to have a pure java solution and stop relying on
po2xml? As well how would that work on windows? And how to make it work
at all :)
This seems to be the last issue as other modules are building fine.
Thanks,
Aleksandar
Aleksandar Kostadinov wrote, On 02/20/2008 01:41 PM (EEST):
> As we talked yesterday it was the pluginRepository entries missing.
>
> Now I get the following error:
>
> [INFO] Processing translation [es-ES]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] unable to obtain appropriate runtime environment
> java.io.IOException: po2xml: not found
> [INFO]
>
> [INFO] Trace
> org.jboss.jdocbook.i18n.actions.process.ExecutionException: unable to
> obtain appropriate runtime environment
> at
> org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:74)
> at
> org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:45)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.generateTranslatedXML(TranslateXmlAction.java:107)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:66)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:80)
> at
> org.jboss.jdocbook.i18n.actions.TranslateXmlAction.perform(TranslateXmlAction.java:50)
> at
> org.jboss.maven.plugins.jdocbook.TranslationMojo.doExecute(TranslationMojo.java:38)
> at
> org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:2
Re: [hibernate-dev] building hibernate trunk
As we talked yesterday it was the pluginRepository entries missing. Now I get the following error: [INFO] Processing translation [es-ES] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] unable to obtain appropriate runtime environment java.io.IOException: po2xml: not found [INFO] [INFO] Trace org.jboss.jdocbook.i18n.actions.process.ExecutionException: unable to obtain appropriate runtime environment at org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:74) at org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:45) at org.jboss.jdocbook.i18n.actions.TranslateXmlAction.generateTranslatedXML(TranslateXmlAction.java:107) at org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:66) at org.jboss.jdocbook.i18n.actions.TranslateXmlAction.po2xml(TranslateXmlAction.java:80) at org.jboss.jdocbook.i18n.actions.TranslateXmlAction.perform(TranslateXmlAction.java:50) at org.jboss.maven.plugins.jdocbook.TranslationMojo.doExecute(TranslationMojo.java:38) at org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:272) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.IOException: java.io.IOException: po2xml: not found at java.lang.UNIXProcess.(UNIXProcess.java:148) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:451) at java.lang.Runtime.exec(Runtime.java:591) at java.lang.Runtime.exec(Runtime.java:429) at java.lang.Runtime.exec(Runtime.java:326) at org.jboss.jdocbook.i18n.actions.process.Executor.execute(Executor.java:60) ... 25 more Any ideas? Thanks, Aleksandar Steve Ebersole wrote, On 02/19/2008 07:33 PM (EEST): > Are you enabling the snapshot repo? > > The built artifact is certainly there... > http://snapshots.jboss.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plugin/2.1.0-SNAPSHOT/ > > > On Feb 19, 2008, at 10:56 AM, Aleksandar Kostadinov wrote: > >> Hello >> >> How can one build hibernate trunk? >> >> I tried to checkout >> http://anonsvn.jboss.org/repos/hibernate/core/trunk/ >> Then first run mvn install on >> http://anonsvn.jboss.org/repos/hibernate/maven-poms/trunk/core-parent/pom.xml >> >> and then mvn install in the checkout dir but I get: >> >> ... >> WAGON_VERSION: 1.0-beta-2 >> [INFO] snapshot >> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.0-SNAPSHOT: checking >> for updates from snapshots.jboss.org >> [INFO] >> >> [ERROR] BUILD ERROR >> [INFO] >> >> [INFO] Plugin could not be found - check that the goal name is correct: >> Unable to download the artifact from any repository >> ... >> >> Can we have everything needed to build it in snapshots.jboss.org? >> >> Thanks much, >> Aleksandar >> __
[hibernate-dev] building hibernate trunk
Hello How can one build hibernate trunk? I tried to checkout http://anonsvn.jboss.org/repos/hibernate/core/trunk/ Then first run mvn install on http://anonsvn.jboss.org/repos/hibernate/maven-poms/trunk/core-parent/pom.xml and then mvn install in the checkout dir but I get: ... WAGON_VERSION: 1.0-beta-2 [INFO] snapshot org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.0-SNAPSHOT: checking for updates from snapshots.jboss.org [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository ... Can we have everything needed to build it in snapshots.jboss.org? Thanks much, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate hudson builds failures
Please ignore last two failure emails from hudson. These were system errors. Regards, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate-oracle9-testsuite Build Completed With Testsuite Errors
It is low on disk space. I'm working to fix. Steve Ebersole wrote, On 06/09/2007 07:15 PM (EEST): > Appears the DB may be down/inaccessible. > > > [EMAIL PROTECTED] wrote: >> View results here -> >> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070609033659 >> >> >> TESTS FAILED >> Ant Error Message: >> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:113: >> The following error occurred while executing this line: >> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:90: >> The following error occurred while executing this line: >> /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: >> Build Successful - Tests completed with errors or failures. >> Date of build: 06/09/2007 03:36:59 >> Time to build: 11 minutes 20 seconds >> >> Unit Tests: (1057) Total Errors and Failures: (267) >> testDistinctIdorg.hibernate.test.id.MultipleHiLoPerTableGeneratorTest >> testRollingBack >> org.hibernate.test.id.MultipleHiLoPerTableGeneratorTest >> testAllParamsorg.hibernate.test.id.MultipleHiLoPerTableGeneratorTest >> testUpdateIdBagorg.hibernate.test.idbag.IdBagTest >> testJoinorg.hibernate.test.idbag.IdBagTest >> testIdClassorg.hibernate.test.idclass.IdClassTest >> testHqlIdPropertyReferences >> org.hibernate.test.idprops.IdentifierPropertyReferencesTest >> testCriteriaIdPropertyReferences >> org.hibernate.test.idprops.IdentifierPropertyReferencesTest >> testImmutableorg.hibernate.test.immutable.ImmutableTest >> testBatchOrderingorg.hibernate.test.insertordering.InsertOrderingTest >> testLazy >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testDirtyCheck >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testFetchAll >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testLazyManyToOne >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testPropertyInitialized >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testManyToOneProxy >> org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest >> testDirtyCheck >> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest >> testPropertyInitialized >> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest >> testManyToOneProxy >> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest >> testLazyPropertyCustomType >> org.hibernate.test.instrument.runtime.JavassistInstrumentationTest >> testCollectionInterceptorg.hibernate.test.interceptor.InterceptorTest >> testPropertyInterceptorg.hibernate.test.interceptor.InterceptorTest >> testPropertyIntercept2org.hibernate.test.interceptor.InterceptorTest >> testComponentInterceptor >> org.hibernate.test.interceptor.InterceptorTest >> testStatefulInterceptorg.hibernate.test.interceptor.InterceptorTest >> testInterfaceProxies >> org.hibernate.test.interfaceproxy.InterfaceProxyTest >> testIterateorg.hibernate.test.iterate.IterateTest >> testScrollorg.hibernate.test.iterate.IterateTest >> testSequentialSelectsorg.hibernate.test.join.JoinTest >> testSequentialSelectsOptionalDataorg.hibernate.test.join.JoinTest >> testAccessAsIncorrectSubclass >> org.hibernate.test.joinedsubclass.JoinedSubclassTest >> testQuerySubclassAttribute >> org.hibernate.test.joinedsubclass.JoinedSubclassTest >> testJoinedSubclass >> org.hibernate.test.joinedsubclass.JoinedSubclassTest >> testLockingJoinedSubclass >> org.hibernate.test.joinedsubclass.JoinedSubclassTest >> testProjectionorg.hibernate.test.joinfetch.JoinFetchTest >> testJoinFetchorg.hibernate.test.joinfetch.JoinFetchTest >> testCollectionFilterorg.hibernate.test.joinfetch.JoinFetchTest >> testJoinFetchManyToManyorg.hibernate.test.joinfetch.JoinFetchTest >> testManyToOneGeneratedIdsOnSave >> org.hibernate.test.jpa.cascade.CascadeTest >> testManyToOneGeneratedIdsorg.hibernate.test.jpa.cascade.CascadeTest >> testManyToOneAssignedIdsorg.hibernate.test.jpa.cascade.CascadeTest >> testOneToOneGeneratedIdsorg.hibernate.test.jpa.cascade.CascadeTest >> testOneToOneAssignedIdsorg.hibernate.test.jpa.cascade.CascadeTest >> testManyToOnePropertyRefGeneratedIds >> org.hibernate.test.jpa.cascade.CascadeTest >> testManyToOnePropertyRefAssignedIds >> org.hibernate.test.jpa.cascade.CascadeTest >> testOneToOnePropertyRefGeneratedIds >> org.hibernate.test.jpa.cascade.CascadeTest >> testOneToOnePropertyRefAssignedIds >> org.hibernate.test.jpa.cascade.CascadeTest >> testLazyorg.hibernate.test.jpa.fetch.FetchingTest >> testHibernateFetchingLazyorg.hibernate.test.jpa.fetch.FetchingTest >> testStaleVersionedInstanceFoundInQueryResult >> org.hibernate.test.jpa.lock.RepeatableReadTest >> testStaleNonVersionedInstanceFoundInQueryResult >> org.hibernate.test.jpa.lock.RepeatableReadTest >> testEjb3ProxyUsageorg.hibernate.test.jpa.proxy.JPAProxyTest >> testGetSemanticsorg.hibernate.test.
Re: [hibernate-dev] hibernate-hsqldb-testsuite build.51 Build Successful
Ok. The change should take effect after few hours. If you encounter any issues, please let me know. Steve Ebersole wrote, On 06/05/2007 02:35 PM (EEST): > I agree it is a bunch of noise at this point. If what Max asks is > possible, then yes lets do that. > > So, to be clear, the request is to get messages when: > 1) Builds are broken > 2) Builds are fixed (i.e. the first working build after breakage). > > Otherwise, leave it as is > > On Tue, 2007-06-05 at 12:19 +0300, Aleksandar Kostadinov wrote: >> Steve, if you also find it a good idea I'll make the change. >> >> Max Rydahl Andersen wrote, On 06/04/2007 11:35 AM (EEST): >>> On Mon, 04 Jun 2007 10:30:32 +0200, Aleksandar Kostadinov >>> <[EMAIL PROTECTED]> wrote: >>> >>>> Max Rydahl Andersen wrote, On 06/04/2007 10:03 AM (EEST): >>>>> Any chance we could start only getting build successful messages after >>>>> something have been fixed ?! >>>> You mean on hibernate-dev@lists.jboss.org or >>>> [EMAIL PROTECTED] >>> Does it matter ? :) >>> >>> But hibernate-dev@lists.jboss.org is the one I see being flooded with >>> multiple >>> consequtive "build succesfull" messages which is more a nuisance than >>> informative ;) >>> >>> /max >>> >>>>> Thus making the only msgs we get the "build failed" + "build fixed" ? >>>>> Everything in between is kinda >>>>> irrelevant is it not ? >>>>> >>>>> /max >>>>> >>>>>> View results here -> >>>>>> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20070603230452Lbuild.51 >>>>>> >>>>>> >>>>>> >>>>>> BUILD COMPLETE - build.51 >>>>>> Date of build: 06/03/2007 23:04:52 >>>>>> Time to build: 10 minutes 22 seconds >>>>>> >>>>>> Unit Tests: (1055) Total Errors and Failures: (0) >>>>>> All Tests Passed >>>>>> >>>>>> Modifications since last build: (first 50 of 0) >>>>>> >>>>> >>>>> >>>>> >>>>> Max Rydahl Andersen >>>>> callto://max.rydahl.andersen >>>>> >>>>> Hibernate >>>>> [EMAIL PROTECTED] >>>>> http://hibernate.org >>>>> >>>>> JBoss a division of Red Hat >>>>> [EMAIL PROTECTED] >>>>> >>> >>> >>> >>> Max Rydahl Andersen >>> callto://max.rydahl.andersen >>> >>> Hibernate >>> [EMAIL PROTECTED] >>> http://hibernate.org >>> >>> JBoss a division of Red Hat >>> [EMAIL PROTECTED] >> ___ >> 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
Re: [hibernate-dev] hibernate-hsqldb-testsuite build.51 Build Successful
Steve, if you also find it a good idea I'll make the change. Max Rydahl Andersen wrote, On 06/04/2007 11:35 AM (EEST): > On Mon, 04 Jun 2007 10:30:32 +0200, Aleksandar Kostadinov > <[EMAIL PROTECTED]> wrote: > >> Max Rydahl Andersen wrote, On 06/04/2007 10:03 AM (EEST): >>> >>> Any chance we could start only getting build successful messages after >>> something have been fixed ?! >> >> You mean on hibernate-dev@lists.jboss.org or >> [EMAIL PROTECTED] > > Does it matter ? :) > > But hibernate-dev@lists.jboss.org is the one I see being flooded with > multiple > consequtive "build succesfull" messages which is more a nuisance than > informative ;) > > /max > >>> >>> Thus making the only msgs we get the "build failed" + "build fixed" ? >>> Everything in between is kinda >>> irrelevant is it not ? >>> >>> /max >>> >>>> View results here -> >>>> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20070603230452Lbuild.51 >>>> >>>> >>>> >>>> BUILD COMPLETE - build.51 >>>> Date of build: 06/03/2007 23:04:52 >>>> Time to build: 10 minutes 22 seconds >>>> >>>> Unit Tests: (1055) Total Errors and Failures: (0) >>>> All Tests Passed >>>> >>>> Modifications since last build: (first 50 of 0) >>>> >>> >>> >>> >>> >>> Max Rydahl Andersen >>> callto://max.rydahl.andersen >>> >>> Hibernate >>> [EMAIL PROTECTED] >>> http://hibernate.org >>> >>> JBoss a division of Red Hat >>> [EMAIL PROTECTED] >>> > > > > > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > [EMAIL PROTECTED] > http://hibernate.org > > JBoss a division of Red Hat > [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate-hsqldb-testsuite build.51 Build Successful
Max Rydahl Andersen wrote, On 06/04/2007 10:03 AM (EEST): > > Any chance we could start only getting build successful messages after > something have been fixed ?! You mean on hibernate-dev@lists.jboss.org or [EMAIL PROTECTED] > > Thus making the only msgs we get the "build failed" + "build fixed" ? > Everything in between is kinda > irrelevant is it not ? > > /max > >> View results here -> >> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20070603230452Lbuild.51 >> >> >> BUILD COMPLETE - build.51 >> Date of build: 06/03/2007 23:04:52 >> Time to build: 10 minutes 22 seconds >> >> Unit Tests: (1055) Total Errors and Failures: (0) >> All Tests Passed >> >> Modifications since last build: (first 50 of 0) >> > > > > > Max Rydahl Andersen > callto://max.rydahl.andersen > > Hibernate > [EMAIL PROTECTED] > http://hibernate.org > > JBoss a division of Red Hat > [EMAIL PROTECTED] > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: sybase setup
I move here http://jira.jboss.com/jira/browse/JBPAPP-196 as I thing this stuff is out of my competence. Aleksandar Kostadinov wrote, On 05/25/2007 04:50 PM (EEST): > Steve Ebersole wrote, On 05/25/2007 04:27 PM (EEST): >> 1) I would guess that this because of temp tables. Hibernate allows the >> Dialect to say whether or not the database supports DDL statements >> within a transaction. Sybase does not override this; the default is to >> query the JDBC metadata to see whether DDL is allowed within >> transactions (see links below). My guess is that Sybase simply does not >> report this accurately based on whether this option you mention is set >> or not set; it probably just blindly says "yeah, we support it...". We >> can look at changing this behavior for Sybase. You can imagine where >> this goes on the priority list ;) > > I would think disabling 'ddl in tran' no matter what sybase reports as > they think it is not good to use it. System tables were locked using > that feature and blah blah... > > Anyway I'm sure you know best what implications will that bring so I > just say what I know and you decide if it makes sense. > >> 2) Believe it or not, as the lead of Hibernate I actually do subscribe >> to the hibernate-dev list ;) >> >> >> http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionCausesTransactionCommit() >> http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionIgnoredInTransactions() >> > > I actually think sybase neither ignores neither commits but just fails > the transaction. I actually haven't experienced it myself. It was Shelly > McGowan who reported the error so I might be wrong. As well it is a per > database option in sybase and could be set for the user databse but not > for the temporary database. > > So it would be a good idea to be at least documented as an issue with > sybase. > >> On Fri, 2007-05-25 at 14:39 +0300, Aleksandar Kostadinov wrote: >>> Looking at the latest hibernate cruisecontrol builds I see around 20 >>> sybase tests are passing because I've enabled "ddl in tran" option of >>> tempdb database. >>> It is not recommended by sybase to use DDL in transactions so I think it >>> should be good to avoid it in future hibernate releases if possible. >>> >>> Regadrs, >>> Aleksandar > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: sybase setup
Steve Ebersole wrote, On 05/25/2007 04:27 PM (EEST): > 1) I would guess that this because of temp tables. Hibernate allows the > Dialect to say whether or not the database supports DDL statements > within a transaction. Sybase does not override this; the default is to > query the JDBC metadata to see whether DDL is allowed within > transactions (see links below). My guess is that Sybase simply does not > report this accurately based on whether this option you mention is set > or not set; it probably just blindly says "yeah, we support it...". We > can look at changing this behavior for Sybase. You can imagine where > this goes on the priority list ;) I would think disabling 'ddl in tran' no matter what sybase reports as they think it is not good to use it. System tables were locked using that feature and blah blah... Anyway I'm sure you know best what implications will that bring so I just say what I know and you decide if it makes sense. > 2) Believe it or not, as the lead of Hibernate I actually do subscribe > to the hibernate-dev list ;) > > > http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionCausesTransactionCommit() > http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionIgnoredInTransactions() > I actually think sybase neither ignores neither commits but just fails the transaction. I actually haven't experienced it myself. It was Shelly McGowan who reported the error so I might be wrong. As well it is a per database option in sybase and could be set for the user databse but not for the temporary database. So it would be a good idea to be at least documented as an issue with sybase. > > On Fri, 2007-05-25 at 14:39 +0300, Aleksandar Kostadinov wrote: >> Looking at the latest hibernate cruisecontrol builds I see around 20 >> sybase tests are passing because I've enabled "ddl in tran" option of >> tempdb database. >> It is not recommended by sybase to use DDL in transactions so I think it >> should be good to avoid it in future hibernate releases if possible. >> >> Regadrs, >> Aleksandar > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] sybase setup
Looking at the latest hibernate cruisecontrol builds I see around 20 sybase tests are passing because I've enabled "ddl in tran" option of tempdb database. It is not recommended by sybase to use DDL in transactions so I think it should be good to avoid it in future hibernate releases if possible. Regadrs, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev][DB2][Was:Fwd: hibernate-oracle9-testsuite Build Completed With Testsuite Errors]
Steve Ebersole wrote on 04/03/2007: > Also, is the db2 instance still accessible? My VPN is finally working > and I finished the release I was working on, so I'll try to look at all > these today. Hi, Have you managed to look at hibernate testsuite hanging on DB2? Could you provide us with any status and/or estimate information? Thanks, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-oracle9-testsuite Build Completed With Testsuite Errors]
Yes, the *instances* are accessible. Please note some tests are hanging only on 7.2 and some only on 8.2 Steve Ebersole wrote: > Also, is the db2 instance still accessible? My VPN is finally working > and I finished the release I was working on, so I'll try to look at all > these today. > > Steve Ebersole wrote: > >> Please send me the server info for the oracle9 instance and the >> postgresql instance. >> >> Are you using the 9i or 10g driver for this oracle9 run? >> >> Aleksandar Kostadinov wrote: >> >>> Hi, >>> >>> new hibernate database build. Now we miss only DB2 ones. >>> >>> Cheers, >>> Aleksandar >>> >>> >>> >>> Subject: >>> hibernate-oracle9-testsuite Build Completed With Testsuite Errors >>> From: >>> [EMAIL PROTECTED] >>> Date: >>> Mon, 2 Apr 2007 16:35:08 -0400 (EDT) >>> To: >>> hibernate-dev@lists.jboss.org, [EMAIL PROTECTED], >>> [EMAIL PROTECTED] >>> >>> To: >>> hibernate-dev@lists.jboss.org, [EMAIL PROTECTED], >>> [EMAIL PROTECTED] >>> >>> >>> View results here -> >>> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070402161846 >>> >>> >>> TESTS FAILED >>> Ant Error Message: >>> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:112: >>> The following error occurred while executing this line: >>> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: >>> The following error occurred while executing this line: >>> /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: >>> Build Successful - Tests completed with errors or failures. >>> Date of build: 04/02/2007 16:18:46 >>> Time to build: 15 minutes 22 seconds >>> Last changed: 04/02/2007 13:40:05 >>> Last log entry: document enhanced id generators >>> >>> Unit Tests: (1048) Total Errors and Failures: (3) >>> testManyToManyFilterOnCriteria >>> org.hibernate.test.filter.DynamicFilterTest >>> testManyToManyFilterOnLoad >>> org.hibernate.test.filter.DynamicFilterTest >>> testFormulaJoin org.hibernate.test.formulajoin.FormulaJoinTest >>> >>> >>> >>> Modifications since last build: (first 50 of 1) >>> 11386 modified [EMAIL PROTECTED] >>> //trunk/Hibernate3/doc/reference/en/modules/basic_mapping.xml >>> document enhanced id generators >>> >>> >>> >>> ___ >>> 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
Re: [hibernate-dev] [Fwd: hibernate-oracle9-testsuite Build Completed With Testsuite Errors]
Steve Ebersole wrote: > Please send me the server info for the oracle9 instance and the > postgresql instance. see hibernate.properties in build artifacts on cc reports page I'm using the same driver for 10g. > > Are you using the 9i or 10g driver for this oracle9 run? > > Aleksandar Kostadinov wrote: > >> Hi, >> >> new hibernate database build. Now we miss only DB2 ones. >> >> Cheers, >> Aleksandar >> >> >> >> Subject: >> hibernate-oracle9-testsuite Build Completed With Testsuite Errors >> From: >> [EMAIL PROTECTED] >> Date: >> Mon, 2 Apr 2007 16:35:08 -0400 (EDT) >> To: >> hibernate-dev@lists.jboss.org, [EMAIL PROTECTED], >> [EMAIL PROTECTED] >> >> To: >> hibernate-dev@lists.jboss.org, [EMAIL PROTECTED], >> [EMAIL PROTECTED] >> >> >> View results here -> >> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070402161846 >> >> >> TESTS FAILED >> Ant Error Message: >> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:112: >> The following error occurred while executing this line: >> /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: >> The following error occurred while executing this line: >> /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: >> Build Successful - Tests completed with errors or failures. >> Date of build: 04/02/2007 16:18:46 >> Time to build: 15 minutes 22 seconds >> Last changed: 04/02/2007 13:40:05 >> Last log entry: document enhanced id generators >> >> Unit Tests: (1048) Total Errors and Failures: (3) >> testManyToManyFilterOnCriteria >> org.hibernate.test.filter.DynamicFilterTest >> testManyToManyFilterOnLoad >> org.hibernate.test.filter.DynamicFilterTest >> testFormulaJoin org.hibernate.test.formulajoin.FormulaJoinTest >> >> >> >> Modifications since last build: (first 50 of 1) >> 11386 modified [EMAIL PROTECTED] >> //trunk/Hibernate3/doc/reference/en/modules/basic_mapping.xml document >> enhanced id generators >> >> >> >> ___ >> 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] [Fwd: hibernate-oracle9-testsuite Build Completed With Testsuite Errors]
Hi, new hibernate database build. Now we miss only DB2 ones. Cheers, Aleksandar --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070402161846 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:112: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 04/02/2007 16:18:46Time to build: 15 minutes 22 secondsLast changed: 04/02/2007 13:40:05Last log entry: document enhanced id generators Unit Tests: (1048) Total Errors and Failures: (3)testManyToManyFilterOnCriteriaorg.hibernate.test.filter.DynamicFilterTesttestManyToManyFilterOnLoadorg.hibernate.test.filter.DynamicFilterTesttestFormulaJoinorg.hibernate.test.formulajoin.FormulaJoinTest Modifications since last build: (first 50 of 1)11386modified[EMAIL PROTECTED]//trunk/Hibernate3/doc/reference/en/modules/basic_mapping.xmldocument enhanced id generators --- End Message --- ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [Fwd: hibernate-sybase-testsuite Build Completed With Testsuite Errors]
http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20070328064843 Many failing tests. Sybase have now 200 connections allowed so this isn't a problem. I've looked at few of the errors and they don't seem to be caused by configuration. Let me know if further server and/or cruisecontrol configuration is required. Thanks, Aleksandar --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20070328064843 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:119: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/28/2007 06:48:43Time to build: 18 minutes 41 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (1046) Total Errors and Failures: (82)testPutAgainstUninitializedMaporg.hibernate.test.collection.map.PersistentMapTesttestUpdateFalseorg.hibernate.test.component.basic.ComponentTesttestComponentorg.hibernate.test.component.basic.ComponentTesttestComponentStateChangeAndDirtinessorg.hibernate.test.component.basic.ComponentTesttestComponentQueriesorg.hibernate.test.component.basic.ComponentTesttestComponentFormulaQueryorg.hibernate.test.component.basic.ComponentTesttestNamedQueryorg.hibernate.test.component.basic.ComponentTesttestMergingorg.hibernate.test.component.cascading.toone.CascadeToComponentAssociationTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.AggressiveReleaseTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.CurrentSessionConnectionTesttestSubselectorg.hibernate.test.criteria.CriteriaQueryTesttestDom4jorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestMapIndexEmisionorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestGeneratedPropertyorg.hibernate.test.generated.TimestampGeneratedValuesWithCachingTesttestCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestStrorg.hibernate.test.hql.ASTParserLoadingTesttestExtractorg.hibernate.test.hql.ASTParserLoadingTesttestEJBQLFunctionsorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestBooleanHandlingorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateWithWhereExistsSubqueryorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnComponentorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnImplicitJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMammalorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullUnionSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestSimpleDeleteOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnMappedJoinorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassAbstractRootorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassConcreteSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassLeafSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteRestrictedOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesReverseorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesPositioningorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestWithClauseFailsWithFetchorg.hibernate.test.hql.WithClauseTesttestWithClauseorg.hibernate.test.hql.WithClauseTesttestInterfaceProxiesorg.hibernate.test.interfaceproxy.InterfaceProxyTesttestJpaStylePositionalParametersInNativeSqlorg.hibernate.test.jpa.ql.NativeQueryTesttestOnCascadeDeleteorg.hibernate.test.legacy.FooBarTesttestCollectionsInSelectorg.hibernate.test.legacy.FooBarTesttestCompositeKeyPathExpressionsorg.
[hibernate-dev] hibernate testsuite on DB2
Hi As you know DB2 7.2 and 8.2 we will test with the DB2 type 4 v9 jdbc driver. With this I don't get the unsupported DDM parameter error on query (DB2 7.2). Haven't done a full run on DB2 8.2 with the ver8 driver but seems to be like with the v9 driver. I've run the testsuite on both 8.2 and 7.2 versions and get similar results. Many tests are failing on both versions. And few lock forever. Steve Ebersole resolved some sybase issues. I hope he will manage to find some time to resolve DB2 locking issues. We need the testsuite at least to be able to complete as this is blocking platform testing. Thanks for your help, Steve! Below is a list of hanging testcases: org.hibernate.test.exception.SQLExceptionConversionTest -7.2 and 8.2 org.hibernate.test.instrument.runtime.CGLIBInstrumentationTest - only 8.2 org.hibernate.test.instrument.runtime.JavassistInstrumentationTest - only 8.2 org.hibernate.test.jpa.lock.JPALockTest -7.2 and 8.2 org.hibernate.test.tm.CMTTest -7.2 and 8.2 junit.instrument.cglib:org.hibernate.test.instrument.buildtime.InstrumentTest - only 8.2 junit.instrument.javassist:org.hibernate.test.instrument.buildtime.InstrumentTest - only 8.2 org.hibernate.test.legacy.FooBarTest -7.2 only once from two runs (not sure about that) org.hibernate.test.typeparameters.TypeParameterTest - only 7.2 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate testsuite on DB2 7.2
Hi I'm trying to setup DB2 7.2 cruisecontrol build but have this: Tests Failures Errors Success rate Time 1043 868633.46% 894.810 I see many "com.ibm.db2.jcc.c.DisconnectException: The DDM parameter is not supported. Unsupported DDM parameter..." My config is: hibernate.dialect org.hibernate.dialect.DB2Dialect hibernate.connection.driver_class com.ibm.db2.jcc.DB2Driver hibernate.connection.url jdbc:db2://dev34.qa.atl.jboss.com:5/jbossqa As you see I'm using the jcc driver which the database should have appropriate bindings for. What could be the reason of these failures? Is there a special dialect for DB2 7.x? Some particular bindings that have to be done so hibernate can work? Thanks, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [Fwd: hibernate-pgsql-testsuite Build Completed With Testsuite Errors]
I will leave sybase build until testsuite is able to complete. I've just setup PostgreSQL build. Please let me know if results seem consistent to you. Thanks, Aleksandar --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-pgsql-testsuite?log=log20070321081030 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:154: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2007 08:10:30Time to build: 20 minutes 53 secondsLast changed: 03/21/2007 07:51:14Last log entry: removed unused dir Unit Tests: (1043) Total Errors and Failures: (17)testComponentQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestQueryorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestBoundedMaterializedBlobAccessorg.hibernate.test.lob.BlobTesttestBoundedBlobLocatorAccessorg.hibernate.test.lob.BlobTesttestUnboundedBlobLocatorAccessorg.hibernate.test.lob.BlobTesttestUnboundedClobLocatorAccessorg.hibernate.test.lob.ClobTesttestManualSynchronizationorg.hibernate.test.sql.GeneralTesttestWhereorg.hibernate.test.where.WhereTesttestBadGrammarorg.hibernate.test.exception.SQLExceptionConversionTesttestPolymorphismorg.hibernate.test.hql.HQLTesttestSubstitutionsorg.hibernate.test.hql.HQLTesttestTokenReplacementorg.hibernate.test.hql.HQLTesttestProductorg.hibernate.test.hql.HQLTesttestExplicitJoinsorg.hibernate.test.hql.HQLTesttestBoundedClobLocatorAccessorg.hibernate.test.lob.ClobTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTest Modifications since last build: (first 50 of 1)11328deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/boaremoved unused dir --- End Message --- ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: hibernate on sybase testsing
Steve Ebersole wrote: > I sent you an email about a month ago asking how to connect. hmmm. can't remember what has happened a month ago... no matter. Hope we'll fix things now. >The > information I have here (which did actually work at one point) no longer > works: > > dev01.jboss.com:4100/tempdb Correct is jdbc:sybase:Tds:dev01.qa.atl.jboss.com:4100/cruisecontrol "dev01" without ".jboss.com" could work also if DNS properly configured. There is tempdb database, but it is not supposed to be used by anyone. > > That was connecting up via the jboss VPN. Now I guess I get to throw RH > VPN in to the mix as well... > Yes. You need the Red Hat VPN *or* use the ssh forwarding stuff many guys prefer over the VPN software. If using ssh I guess you should pass -L4100:dev01.qa.atl.jboss.com:4100 and use jdbc:sybase:Tds:localhost:4100/cruisecontrol connection url. If you have problems accessing the QA Lab can contact me directly. Regards, Aleksandar > > Aleksandar Kostadinov wrote: > >> Were you able to run the hibernate testsuite on sybase in the QA Lab? >> As we updated it to 12.5.3 latest fixpack I tried to run it again. >> Results are the same. >> >> testManualDisconnectWithOpenResources from >> org.hibernate.test.connections.SuppliedConnectionTest locks the build. >> >> Hope that helps. >> Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] sybase
Steve Ebersole wrote: > That or we could get these DB instances externally accessible rather > than needing VPN + tunneling + black-voodoo-magic ;) Only VPN. Inside the VPN (currently JBoss, soon the Red Hat one) you can directly access hosts in the QA lab on any port. No magic (only a great luck ;) > Well, I'd need to know the test that locks up the DB (and the results > are not pushing to the CC site). The strange part is that neither of > these tests is even testing concurrent access; they (should) deal with a > single connection at a time. Is locking in Sybase so good that a > connection can block itself ;) hmmm... I can't imagine why. I see many connections, one of them in a state "lock wait". Killing one by one and testsuite continues at some point. I think it would be best to run the testsuite by yourself. If you need any information about QA lab access, where to find jdbc drivers etc. you may contact me. > > -Original Message- > From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 2:21 PM > To: Steve Ebersole > Cc: hibernate-dev@lists.jboss.org > Subject: Re: [hibernate-dev] sybase > > See answers below. btw if you are inside jboss VPN, you could run the > testsuite on the sybase db from your local computer or from one of the > QA machines. > > Steve Ebersole wrote: > >>Which specific test methods in the two tests you mention fail with > > locking issues? > > Don't know. > > >>Also what is the exact Sybase product and version you are using? > > Adaptive Server Enterprise/12.5.2/EBF > > >>What is the isolation of the Sybase JDBC connections? > > Default? We can add this to hibernate.properties > > >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, January 24, 2007 9:21 AM >>To: Steve Ebersole >>Cc: hibernate-dev@lists.jboss.org >>Subject: Re: [hibernate-dev] sybase >> >>Are you going to do something about sybase or leave it at least for > > now? > >>Thanks, >>Aleksandar >> >>- >>I cleaned up database again and ran the following command: >>./build.sh >>-Djar.driver=/opt/jdbc-drivers/jConnect-6_0/classes/jconn3.jar >>-Dhibernate.test.validatefailureexpected=true junitreport >> >>The testsuite locked on these testsuites: >>org.hibernate.test.connections.SuppliedConnectionTest >>org.hibernate.test.connections.ThreadLocalCurrentSessionTest >> >>hibernate.properties contains: >>hibernate.dialect org.hibernate.dialect.SybaseDialect >>hibernate.connection.driver_class com.sybase.jdbc3.jdbc.SybDriver >>hibernate.connection.username >>hibernate.connection.password >>hibernate.connection.url jdbc:sybase:Tds:dev01:4100/ >> >>btw. there were many failing tests >> >>Aleksandar Kostadinov wrote: >> >> >> >>>In the new year I could do more investigations about that. For now I >>>can only tell there are more than one. >>> >>>Steve Ebersole wrote: >>> >>> >>> >>>>I do not have a local Sybase install against which to test. However, >>>>that would not surprise me. Can you tell me the tests during which > > it > >>>>locks up? >>>> >>>>-Original Message- >>>>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>>>Sent: Friday, December 22, 2006 1:13 PM >>>>To: Steve Ebersole >>>>Cc: hibernate-dev@lists.jboss.org >>>>Subject: Re: [hibernate-dev] sybase >>>> >>>>Using either 6.05 or 5.5 results in locks. >>>>Are you able to run the testsuite against sybase at all? >>>> >>>>Aleksandar Kostadinov wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Should I use the latest jconnect6.05 for sybase tests? >>>>> >>>>>Thanks, >>>>>Aleksandar >>>>>___ >>>>>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
Re: [hibernate-dev] sybase
See answers below. btw if you are inside jboss VPN, you could run the testsuite on the sybase db from your local computer or from one of the QA machines. Steve Ebersole wrote: > Which specific test methods in the two tests you mention fail with locking issues? Don't know. > Also what is the exact Sybase product and version you are using? Adaptive Server Enterprise/12.5.2/EBF > What is the isolation of the Sybase JDBC connections? Default? We can add this to hibernate.properties > -Original Message- > From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 9:21 AM > To: Steve Ebersole > Cc: hibernate-dev@lists.jboss.org > Subject: Re: [hibernate-dev] sybase > > Are you going to do something about sybase or leave it at least for now? > > Thanks, > Aleksandar > > - > I cleaned up database again and ran the following command: > ./build.sh > -Djar.driver=/opt/jdbc-drivers/jConnect-6_0/classes/jconn3.jar > -Dhibernate.test.validatefailureexpected=true junitreport > > The testsuite locked on these testsuites: > org.hibernate.test.connections.SuppliedConnectionTest > org.hibernate.test.connections.ThreadLocalCurrentSessionTest > > hibernate.properties contains: > hibernate.dialect org.hibernate.dialect.SybaseDialect > hibernate.connection.driver_class com.sybase.jdbc3.jdbc.SybDriver > hibernate.connection.username > hibernate.connection.password > hibernate.connection.url jdbc:sybase:Tds:dev01:4100/ > > btw. there were many failing tests > > Aleksandar Kostadinov wrote: > > >>In the new year I could do more investigations about that. For now I >>can only tell there are more than one. >> >>Steve Ebersole wrote: >> >> >>>I do not have a local Sybase install against which to test. However, >>>that would not surprise me. Can you tell me the tests during which it >>>locks up? >>> >>>-Original Message- >>>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>>Sent: Friday, December 22, 2006 1:13 PM >>>To: Steve Ebersole >>>Cc: hibernate-dev@lists.jboss.org >>>Subject: Re: [hibernate-dev] sybase >>> >>>Using either 6.05 or 5.5 results in locks. >>>Are you able to run the testsuite against sybase at all? >>> >>>Aleksandar Kostadinov wrote: >>> >>> >>> >>> >>>>Should I use the latest jconnect6.05 for sybase tests? >>>> >>>>Thanks, >>>>Aleksandar >>>>___ >>>>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
Re: [hibernate-dev] sybase
Are you going to do something about sybase or leave it at least for now? Thanks, Aleksandar - I cleaned up database again and ran the following command: ./build.sh -Djar.driver=/opt/jdbc-drivers/jConnect-6_0/classes/jconn3.jar -Dhibernate.test.validatefailureexpected=true junitreport The testsuite locked on these testsuites: org.hibernate.test.connections.SuppliedConnectionTest org.hibernate.test.connections.ThreadLocalCurrentSessionTest hibernate.properties contains: hibernate.dialect org.hibernate.dialect.SybaseDialect hibernate.connection.driver_class com.sybase.jdbc3.jdbc.SybDriver hibernate.connection.username hibernate.connection.password hibernate.connection.url jdbc:sybase:Tds:dev01:4100/ btw. there were many failing tests Aleksandar Kostadinov wrote: > In the new year I could do more investigations about that. For now I > can only tell there are more than one. > > Steve Ebersole wrote: > >>I do not have a local Sybase install against which to test. However, >>that would not surprise me. Can you tell me the tests during which it >>locks up? >> >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Friday, December 22, 2006 1:13 PM >>To: Steve Ebersole >>Cc: hibernate-dev@lists.jboss.org >>Subject: Re: [hibernate-dev] sybase >> >>Using either 6.05 or 5.5 results in locks. >>Are you able to run the testsuite against sybase at all? >> >>Aleksandar Kostadinov wrote: >> >> >> >>>Should I use the latest jconnect6.05 for sybase tests? >>> >>>Thanks, >>>Aleksandar >>>___ >>>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
Re: [hibernate-dev] sybase
I cleaned up database again and ran the following command: ./build.sh -Djar.driver=/opt/jdbc-drivers/jConnect-6_0/classes/jconn3.jar -Dhibernate.test.validatefailureexpected=true junitreport The testsuite locked on these testsuites: org.hibernate.test.connections.SuppliedConnectionTest org.hibernate.test.connections.ThreadLocalCurrentSessionTest hibernate.properties contains: hibernate.dialect org.hibernate.dialect.SybaseDialect hibernate.connection.driver_class com.sybase.jdbc3.jdbc.SybDriver hibernate.connection.username hibernate.connection.password hibernate.connection.url jdbc:sybase:Tds:dev01:4100/ btw. there were many failing tests Aleksandar Kostadinov wrote: > In the new year I could do more investigations about that. For now I > can only tell there are more than one. > > Steve Ebersole wrote: > >>I do not have a local Sybase install against which to test. However, >>that would not surprise me. Can you tell me the tests during which it >>locks up? >> >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Friday, December 22, 2006 1:13 PM >>To: Steve Ebersole >>Cc: hibernate-dev@lists.jboss.org >>Subject: Re: [hibernate-dev] sybase >> >>Using either 6.05 or 5.5 results in locks. >>Are you able to run the testsuite against sybase at all? >> >>Aleksandar Kostadinov wrote: >> >> >> >>>Should I use the latest jconnect6.05 for sybase tests? >>> >>>Thanks, >>>Aleksandar >>>___ >>>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
Re: [hibernate-dev] sybase
In the new year I could do more investigations about that. For now I can only tell there are more than one. Steve Ebersole wrote: I do not have a local Sybase install against which to test. However, that would not surprise me. Can you tell me the tests during which it locks up? -Original Message- From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]] Sent: Friday, December 22, 2006 1:13 PM To: Steve Ebersole Cc: hibernate-dev@lists.jboss.org Subject: Re: [hibernate-dev] sybase Using either 6.05 or 5.5 results in locks. Are you able to run the testsuite against sybase at all? Aleksandar Kostadinov wrote: Should I use the latest jconnect6.05 for sybase tests? Thanks, Aleksandar ___ 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
Re: [hibernate-dev] sybase
Using either 6.05 or 5.5 results in locks. Are you able to run the testsuite against sybase at all? Aleksandar Kostadinov wrote: >Should I use the latest jconnect6.05 for sybase tests? > >Thanks, >Aleksandar >___ >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] sybase
Should I use the latest jconnect6.05 for sybase tests? Thanks, Aleksandar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [Fwd: hibernate-sqlserver-msjdbc-testsuite Build Completed With Testsuite Errors]
Hi. Look at the results. Hope you'll not need more sqlserver tests ;) Cheers, Aleksandar --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-msjdbc-testsuite?log=log20061218082155 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/18/2006 08:21:55Time to build: 11 minutes 13 seconds Unit Tests: (1028) Total Errors and Failures: (3)testReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestManyToManyWithFormulaorg.hibernate.test.manytomany.ManyToManyTesttestCachedCollectionRefreshorg.hibernate.test.legacy.MasterDetailTest Modifications since last build: (first 50 of 0) --- End Message --- ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: hibernate-oracle10-testsuite Build Completed With Testsuite Errors
It's now fixed. http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20061216143922 Steve Ebersole wrote: > This one at least is able to find the driver. The issue appears to be > either connectivity or perhaps a bad connection URL. > > > BTW, what is the purpose of the ‘hibernate.properties’ in the result > artifacts? This one, for example, shows a HSQL configuration… > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: Hibernate test suite
It is very strange that copying the file to the lib dir makes things
work. I tried to replace where in build.xml jar.driver is set to hsql,
but that didn't worked also.
Any ideas?
Aleksandar Kostadinov wrote:
> Yeah, I see that the problem is not finding the jdbc driver. I meant
> that all other databases tests fail with a new reason, but the same
> for all of them.
> I asked you if there is a change in how hibernate searches for it.
> Cruisecontrol invokes ant with the following pratameters:
> -Djar.driver=${driver.jar}
> -Dhibernate.test.validatefailureexpected=true
> -lib lib
>
> Here driver.jar is the jdbc driver location. Is there some change that
> prevents this from working and is it possible to make this work.
>
> Steve Ebersole wrote:
>
>>No the failures are different. Previously we were getting NPE; now CCE.
>>
>>The tests run fine for me in my IDE. The only way I have been able to
>>reproduce such a CCE is for the JDBC driver to be unavailable when the
>>junit task starts up. This causes the constructor of one of the test
>>classes to fail, which JUnit handles by creating a "stand-in" test case
>>of type an inner type as defined in the TestSuite.warning() method. I
>>have added extra protections to allow non-FunctionalTestCase instance to
>>be handled by the FunctionalTestClassTestSuite which I will be checking
>>in soon.
>>
>>In the meantime, I would assume this indicates a problem with the CC
>>test runs not being able to find the drivers. Hard to tell without the
>>stack trace and error log...
>>
>>
>>-Original Message-
>>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]
>>Sent: Wednesday, December 13, 2006 3:30 AM
>>To: Steve Ebersole
>>Cc: hibernate-dev@lists.jboss.org
>>Subject: Re: Hibernate test suite
>>
>>Only hsql tests work.
>>
>>Other databases tests fail with the same reason.
>>
>>Is there a change in the way testsuite should be ran? How to set jdbc
>>driver? Properties file changes?
>>
>>Steve Ebersole wrote:
>>
>>
>>
>>>I am just now checking in the reorganization of the Hibernate test
>>>
>>>
>>suite
>>
>>
>>>I have been working on for the last few days.
>>>
>>>The main piece is the addition of the org.hibernate.junit package in
>>>
>>>
>>the
>>
>>
>>>test source directory. Specifically, tests in the test suite now have
>>>two well defined flavors:
>>>1) org.hibernate.junit.UnitTestCase
>>>2) org.hibernate.junit.functional.FunctionalTestCase
>>>
>>>The vast majority of the Hibernate test suite falls into the later
>>>category...
>>>
>>>Also, a new custom TestSuite subclass was introduced for
>>>FunctionalTestCase classes
>>>(org.hibernate.junit.functional.FunctionalTestClassTestSuite).
>>>FunctionalTestCase classes should use this custom test suite from their
>>>suite() method. The main reason for this set up is to allow better
>>>sharing of a SessionFactory between TestCase methods. Previously, the
>>>org.hibernate.test.TestCase class had this responsibility. The
>>>
>>>
>>problems
>>
>>
>>>being that it did not have visibility into when the "run" completed.
>>>
>>>
>>So
>>
>>
>>>it just left the schema for the last run test hanging around. This new
>>>set up makes sure that does not happen, because it is the test suite
>>>which is responsible for building/closing the SessionFactory.
>>>FunctionalTestCase does build a SessionFactory if one is not injected
>>>into it by FunctionalTestClassTestSuite (or some other source). It
>>>considers this a "locally managed" SessionFactory which will get closed
>>>after the completion of the test method; this is for running a single
>>>method in an IDE.
>>>
>>>Anyway, the test suite should start working again ;)
>>>
>>>
>>>
>>>
>>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: Hibernate test suite
Yeah, I see that the problem is not finding the jdbc driver. I meant
that all other databases tests fail with a new reason, but the same for
all of them.
I asked you if there is a change in how hibernate searches for it.
Cruisecontrol invokes ant with the following pratameters:
-Djar.driver=${driver.jar}
-Dhibernate.test.validatefailureexpected=true
-lib lib
Here driver.jar is the jdbc driver location. Is there some change that
prevents this from working and is it possible to make this work.
Steve Ebersole wrote:
>No the failures are different. Previously we were getting NPE; now CCE.
>
>The tests run fine for me in my IDE. The only way I have been able to
>reproduce such a CCE is for the JDBC driver to be unavailable when the
>junit task starts up. This causes the constructor of one of the test
>classes to fail, which JUnit handles by creating a "stand-in" test case
>of type an inner type as defined in the TestSuite.warning() method. I
>have added extra protections to allow non-FunctionalTestCase instance to
>be handled by the FunctionalTestClassTestSuite which I will be checking
>in soon.
>
>In the meantime, I would assume this indicates a problem with the CC
>test runs not being able to find the drivers. Hard to tell without the
>stack trace and error log...
>
>
>-Original Message-
>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, December 13, 2006 3:30 AM
>To: Steve Ebersole
>Cc: hibernate-dev@lists.jboss.org
>Subject: Re: Hibernate test suite
>
>Only hsql tests work.
>
>Other databases tests fail with the same reason.
>
>Is there a change in the way testsuite should be ran? How to set jdbc
>driver? Properties file changes?
>
>Steve Ebersole wrote:
>
>
>
>>I am just now checking in the reorganization of the Hibernate test
>>
>>
>suite
>
>
>>I have been working on for the last few days.
>>
>>The main piece is the addition of the org.hibernate.junit package in
>>
>>
>the
>
>
>>test source directory. Specifically, tests in the test suite now have
>>two well defined flavors:
>>1) org.hibernate.junit.UnitTestCase
>>2) org.hibernate.junit.functional.FunctionalTestCase
>>
>>The vast majority of the Hibernate test suite falls into the later
>>category...
>>
>>Also, a new custom TestSuite subclass was introduced for
>>FunctionalTestCase classes
>>(org.hibernate.junit.functional.FunctionalTestClassTestSuite).
>>FunctionalTestCase classes should use this custom test suite from their
>>suite() method. The main reason for this set up is to allow better
>>sharing of a SessionFactory between TestCase methods. Previously, the
>>org.hibernate.test.TestCase class had this responsibility. The
>>
>>
>problems
>
>
>>being that it did not have visibility into when the "run" completed.
>>
>>
>So
>
>
>>it just left the schema for the last run test hanging around. This new
>>set up makes sure that does not happen, because it is the test suite
>>which is responsible for building/closing the SessionFactory.
>>FunctionalTestCase does build a SessionFactory if one is not injected
>>into it by FunctionalTestClassTestSuite (or some other source). It
>>considers this a "locally managed" SessionFactory which will get closed
>>after the completion of the test method; this is for running a single
>>method in an IDE.
>>
>>Anyway, the test suite should start working again ;)
>>
>>
>>
>>
>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: Hibernate test suite
Only hsql tests work. Other databases tests fail with the same reason. Is there a change in the way testsuite should be ran? How to set jdbc driver? Properties file changes? Steve Ebersole wrote: >I am just now checking in the reorganization of the Hibernate test suite >I have been working on for the last few days. > >The main piece is the addition of the org.hibernate.junit package in the >test source directory. Specifically, tests in the test suite now have >two well defined flavors: >1) org.hibernate.junit.UnitTestCase >2) org.hibernate.junit.functional.FunctionalTestCase > >The vast majority of the Hibernate test suite falls into the later >category... > >Also, a new custom TestSuite subclass was introduced for >FunctionalTestCase classes >(org.hibernate.junit.functional.FunctionalTestClassTestSuite). >FunctionalTestCase classes should use this custom test suite from their >suite() method. The main reason for this set up is to allow better >sharing of a SessionFactory between TestCase methods. Previously, the >org.hibernate.test.TestCase class had this responsibility. The problems >being that it did not have visibility into when the "run" completed. So >it just left the schema for the last run test hanging around. This new >set up makes sure that does not happen, because it is the test suite >which is responsible for building/closing the SessionFactory. >FunctionalTestCase does build a SessionFactory if one is not injected >into it by FunctionalTestClassTestSuite (or some other source). It >considers this a "locally managed" SessionFactory which will get closed >after the completion of the test method; this is for running a single >method in an IDE. > >Anyway, the test suite should start working again ;) > > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors]
It is in the setup guide. I think testing with the ms driver should not be a problem. I'll continue to add databases when testsuite gets repaired. Steve Ebersole wrote: >ALTER DATABASE is OK. We just need to make sure this shows up in your >setup guide in case we need to recreate this db instance or setup >another. > >As for the driver, I would prefer the use of the mssql driver. What's >the possibility of running with both? > > >-Original Message- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 12, 2006 3:27 AM >To: Steve Ebersole; hibernate-dev@lists.jboss.org >Subject: [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With >Testsuite Errors] > >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
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
Re: [hibernate-dev] [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors]
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
[hibernate-dev] [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors]
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] [Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors]
Hi. As you see I used jtds driver for this one. It doesn't support setting the transaction isolation level to snapshot, but I tuned 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 runned 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 cruesecintrol 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. --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds-testsuite?log=log20061207113515 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:120: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/07/2006 11:35:15Time to build: 10 minutes 39 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (953) Total Errors and Failures: (8)testOnCascadeDeleteorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestManyToManyPropertyReforg.hibernate.test.propertyref.basic.PropertyRefTesttestUnionSubclassorg.hibernate.test.unionsubclass2.UnionSubclassTesttestImplicitJoinsInDifferentClausesorg.hibernate.test.hql.ASTParserLoadingTesttestExpressionWithParamInFunctionorg.hibernate.test.hql.HQLTesttestConcatenationorg.hibernate.test.hql.HQLTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.basic.PropertyRefTest Modifications since last build: (first 50 of 2384)10945modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/WithClauseTest.javaspecialized InvalidWithClauseException10945modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/HqlSqlWalker.javaspecialized InvalidWithClauseException10945added[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/InvalidWithClauseException.javaspecialized InvalidWithClauseException10943modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ASTParserLoadingTest.javaremoved FailureExpected10941modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/CrazyIdFieldNames.hbm.xmltest failures - shallow + implicit joins10941modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ASTParserLoadingTest.javatest failures - shallow + implicit joins10941modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/HQLTest.javatest failures - shallow + implicit joins10941modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/tree/DotNode.javatest failures - shallow + implicit joins10939modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/jdbc/ConnectionManager.javabug in borrowed connection releasing10936modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/Dialect.javaHHH-2221 : MySQL and temporary table creation10936modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/MySQLDialect.javaHHH-2221 : MySQL and temporary table creation10936modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/TestCase.javaHHH-2221 : MySQL and temporary table creation10936modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/Cache71Dialect.javaHHH-2221 : MySQL and temporary table creation10936modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/exec/AbstractStatementExecutor.javaHHH-2221 : MySQL and temporary table creation10936modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/BulkManipulationTest.javaHHH-2221 : MySQL and temporary table creation10933modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/tree/DotNode.java(follow-on) HHH-2257 : implicit joins and shallow queries10932modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/HQLTest.javaHHH-2284 : HQL + sub-component references10932added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ComponentContainer.javaHHH-2284 : HQL + sub-component references10932added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ComponentContainer.hbm.xmlHHH-2284 : HQL + sub-component references10932modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/tree/DotNode.javaHHH-2284 : HQL + sub-component references10932modified[EMAIL PROTECTED]//trunk/Hiber
[hibernate-dev] Re: oracle test results
I've updated the driver to 10.2.0.2 You should be able to see the new results in half an hour. Steve Ebersole wrote: >OK, I just tracked down the cause of the failures I found disturbing >with the hibernate-oracle-10g testsuite. Y'all are using a much older >driver: >22:32:44,850 INFO SettingsFactory:82 - JDBC driver: Oracle JDBC driver, >version: 10.1.0.3.0 > >We should be using some 10.2.x series driver. Locally I use 10.2.0.1.0; >they are up to 10.2.0.2 (either of which should work): >http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html > >This is the cause (I believe) for failures in: >org.hibernate.test.lob.BlobTest#testBoundedMaterializedBlobAccess >org.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTest#testSe >quenceIdentityGenerator > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
Just to inform that we are now using MySQL5innodbdialect (for 5.0 tests) with the mysql 5 jdbc driver. Steve Ebersole wrote: >Yes, you should use the MySQL5Dialect... > >For SQLServer you must: >1) use 2005 and the correspnding MS driver (no jTDS!) >2) use the snapshot isolation level (hibernate.connection.isolation >4096) >Otherwise, yes that (and others, I believe) will hang. > >Here are my local settings for SQLServer (2005 Express): >hibernate.dialect org.hibernate.dialect.SQLServerDialect >hibernate.connection.url jdbc:sqlserver://localhost:1681 >hibernate.connection.driver_class >com.microsoft.sqlserver.jdbc.SQLServerDriver >hibernate.connection.isolation 4096 >hibernate.connection.username hibernate >hibernate.connection.password hibernate > > > >-Original Message- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 05, 2006 2:04 PM >To: Steve Ebersole; hibernate-dev@lists.jboss.org >Subject: Re: [Fwd: hibernate-mysql50-testsuite Build Completed With >Testsuite Errors] > >Yes. The tests run with the innodb dialect. Prabhat mentioned that there >is a separate dialect for mysql5. Should I set it for tests on mysql >5.0? > >There is a problem with the SQL server tests. EJB3LockTest freezes >things until build timeout comes. Is it possible to set per test >timeouts so a single test cannot break the whole build? Or say if any >test/testcase takes longer than a minute then fail it and continue? > >EJB3LockTest should be disabled or repaired so I can enable regular >SQLserver tests. > >Thanks. > >Steve Ebersole wrote: > > > >>Another question. Did you create this with InnoDB as the default >>engine? If not, please do so. Running with MyISAM is not an accurate >>representation of a valid production environment. >> >>Thanks. >> >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Sunday, December 03, 2006 6:18 AM >>To: hibernate-dev@lists.jboss.org; Steve Ebersole >>Subject: [Fwd: hibernate-mysql50-testsuite Build Completed With >>Testsuite Errors] >> >>As failings with mysql 5.0.27 are similar to these of 4.1.22 I consider >>results are consistent. >> >>Please contact me if you don't agree. >> >> >> >> ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]
I mean is it possible to have a testcase which only tries to clean everithing from the database it has connection to. So it is not connected with other tests. It could not use junit at all. It will be best to have a separate target (say cleandb) and when we run "build.sh cleandb" we know that the database is ok. Steve Ebersole wrote: >It should only be a problem with the last of the test cases. Basically, >Hibernate tries to create and drop the schema needed for a particular >test class once. However, this ability to run some piece of code once >per test class is a deficiency in JUnit. The Hibernate test suite tries >to achieve that by some magic in on overridden version of setup. > >AFAICT, the only real options involve using a different test framework. >TestNG (or even JUnit4 for that matter) offer the ability to perform >initialization and clean-up *once per test class*. > >The other alternative is to (re)create the schema as part of >setup/teardown for *each test method*, which is unacceptable. > >Perhaps something could be achieved by extension of JUnit. I had >previously looked at junit.extensions.TestSetup for example. But that >required pretty extensive changes to the test suite to accommodate. > >I am certainly open to suggestions... > >-Original Message- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Monday, December 04, 2006 2:56 PM >To: Darryl Miles; Steve Ebersole; hibernate-dev@lists.jboss.org >Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build >CompletedWith Testsuite Errors] > >Now we test with mysql connector 5.0.4 > >Darryl, you want to see some info on the first page or in the >host-version-info.txt? >I see the latter easier to achieve and at this time cannot say anything >about the first one. >Anyway in this repo you can find the cruisecontrol configuration files >svn.jboss.org/repos/qa/cruisecontrol/trunk/ >scripts/cruisecontrol/build-hibernate-db-matrix.xml is the build file >for hibernate >target to look at is maybe copyresults (just on my first look) > >I think that if it will be very useful for developers such a thing could >be done but I see another problem with hibernate tests that should be >resolved. I see tables and procedures not dropped after the tests and I >think after some time they break things. Could you think of something >that cleans the database defore testing or after testing? Is it possible >to create a target in the hibernate's build file which cleans the >database and nothing else? That ways you could get more accurate results >and in case of database connectivity problems only qa team get informed. > >Darryl Miles wrote: > > > >>Steve Ebersole wrote: >> >> >>>Um, perhaps if you are going to ask me to do something you could can >>> >>> >>the >> >> >>>attitude? Seems like a basic requirement to me... >>> >>> >>Sorry if I put words in your mouth there or seem to be creating lots >>of work for somebody else. >> >>Is the cruise control configuration / testing regime checked into a >>repository; maybe I can assist with these changes and attach a patch >>rather than open a JIRA feature request ? >> >> >>Darryl >> >> > > > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
jtds guys say their driver is recommended for hibernate ;) Only this one hangs. It's not a problem to use the MS jdbc driver but is it necessary to run on 2005. We now have only 2000. Steve Ebersole wrote: >Yes, you should use the MySQL5Dialect... > >For SQLServer you must: >1) use 2005 and the correspnding MS driver (no jTDS!) >2) use the snapshot isolation level (hibernate.connection.isolation >4096) >Otherwise, yes that (and others, I believe) will hang. > >Here are my local settings for SQLServer (2005 Express): >hibernate.dialect org.hibernate.dialect.SQLServerDialect >hibernate.connection.url jdbc:sqlserver://localhost:1681 >hibernate.connection.driver_class >com.microsoft.sqlserver.jdbc.SQLServerDriver >hibernate.connection.isolation 4096 >hibernate.connection.username hibernate >hibernate.connection.password hibernate > > > >-Original Message- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 05, 2006 2:04 PM >To: Steve Ebersole; hibernate-dev@lists.jboss.org >Subject: Re: [Fwd: hibernate-mysql50-testsuite Build Completed With >Testsuite Errors] > >Yes. The tests run with the innodb dialect. Prabhat mentioned that there >is a separate dialect for mysql5. Should I set it for tests on mysql >5.0? > >There is a problem with the SQL server tests. EJB3LockTest freezes >things until build timeout comes. Is it possible to set per test >timeouts so a single test cannot break the whole build? Or say if any >test/testcase takes longer than a minute then fail it and continue? > >EJB3LockTest should be disabled or repaired so I can enable regular >SQLserver tests. > >Thanks. > >Steve Ebersole wrote: > > > >>Another question. Did you create this with InnoDB as the default >>engine? If not, please do so. Running with MyISAM is not an accurate >>representation of a valid production environment. >> >>Thanks. >> >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Sunday, December 03, 2006 6:18 AM >>To: hibernate-dev@lists.jboss.org; Steve Ebersole >>Subject: [Fwd: hibernate-mysql50-testsuite Build Completed With >>Testsuite Errors] >> >>As failings with mysql 5.0.27 are similar to these of 4.1.22 I consider >>results are consistent. >> >>Please contact me if you don't agree. >> >> >> >> ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
Yes. The tests run with the innodb dialect. Prabhat mentioned that there is a separate dialect for mysql5. Should I set it for tests on mysql 5.0? There is a problem with the SQL server tests. EJB3LockTest freezes things until build timeout comes. Is it possible to set per test timeouts so a single test cannot break the whole build? Or say if any test/testcase takes longer than a minute then fail it and continue? EJB3LockTest should be disabled or repaired so I can enable regular SQLserver tests. Thanks. Steve Ebersole wrote: >Another question. Did you create this with InnoDB as the default >engine? If not, please do so. Running with MyISAM is not an accurate >representation of a valid production environment. > >Thanks. > >-Original Message----- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Sunday, December 03, 2006 6:18 AM >To: hibernate-dev@lists.jboss.org; Steve Ebersole >Subject: [Fwd: hibernate-mysql50-testsuite Build Completed With >Testsuite Errors] > >As failings with mysql 5.0.27 are similar to these of 4.1.22 I consider >results are consistent. > >Please contact me if you don't agree. > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
Darryl,
For the information you wish, you could create a JIRA task (maybe a
feature request).
I will update the the JDBC driver to the latest.
Tanks for the feedback.
Aleksandar
Darryl Miles wrote:
>
> Is it possible to emit some extra information with the testsuite
> output summary.
>
>
>
> The host running the testsuites JDK and Operating System (whichever
> values seems more useful across the major JDK) :
>
> java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
> java.runtime.version=1.5.0_08-b03
> java.specification.version=1.5
> java.vendor=Sun Microsystems Inc.
> java.version=1.5.0_08
> os.arch=amd64
> os.name=Linux
> os.version=2.6.18
>
>
> Infact the above is hidden away in host-version-info.txt, but surely
> the above information can be summarized into a single line and emitted
> with the test suite for all to clearly see.
>
> Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_08) Sun
> Microsystems Inc. [Linux amd64 2.6.18]
>
> "java.runtime.name" ("java.version") "java.vendor" ["os.name"
> "os.arch" "os.version"]
>
>
>
>
> Also the same with the exact SQL server version and the JDBC driver
> version, maybe also a new "jdbc-version-info.txt" should be created too:
>
> On MySQL a 'SELECT VERSION();' gets the server version but a more
> generic way maybe to use:
>
> java.sql.Connection.getServerMajorVersion() = 5
> java.sql.Connection.getServerMinorVersion() = 0
> java.sql.Connection.getSubMinorVersion() = 22
> java.sql.Connection.getServerVersion() = "MySQL, version:
> 5.0.27-standard-log" ??
>
> java.sql.Driver.getMajorVersion() = "3"
> java.sql.Driver.getMinorVersion() = "1"
>
> java.sql.Connection.getMetaData().getDriverVersion() = "MySQL-AB JDBC
> Driver, version: mysql-connector-java-3.1.10 ( $Date: 2005/05/19
> 15:52:23 $, $Revision: 1.1.2.2 $ )"
>
>
>
> Looking at your test suite you are running with 3.1.10 JDBC driver, I
> know for sure that 3.1.13 is buggy with hibernate as I had to upgrade
> from it. This was in relation to unsigned data handling into signed
> java types (UNSIGNED TINYINT (0-255) -> short). Please consider
> 3.1.14 or later.
>
> Also JDBC driver 5.0.x is considered GA now looking at the MySQL
> website. Is the 5.0.x driver a necessary upgrade to get access to
> some of the features of the 5.0.x MySQL server ? I would recommend
> maybe using mysql-connector-java-5.0.x with MySQL 5.0.x.
>
>
> Darryl
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
As failings with mysql 5.0.27 are similar to these of 4.1.22 I consider results are consistent. Please contact me if you don't agree. --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061203061513 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:134: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/03/2006 06:15:13Time to build: 26 minutes 35 seconds Unit Tests: (943) Total Errors and Failures: (47)testCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestBooleanHandlingorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateWithWhereExistsSubqueryorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnComponentorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnImplicitJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMammalorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullUnionSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnMappedJoinorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassAbstractRootorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassConcreteSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassLeafSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteWithMetadataWhereFragmentsorg.hibernate.test.hql.BulkManipulationTesttestDeleteRestrictedOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesReverseorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesPositioningorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestWithClauseFailsWithFetchorg.hibernate.test.hql.WithClauseTesttestWithClauseorg.hibernate.test.hql.WithClauseTesttestInterfaceProxiesorg.hibernate.test.interfaceproxy.InterfaceProxyTesttestQueryorg.hibernate.test.legacy.FooBarTesttestOneToOneGeneratororg.hibernate.test.legacy.FooBarTesttestReachabilityorg.hibernate.test.legacy.FooBarTesttestVersionedCollectionsorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestOneToManyLinkTableorg.hibernate.test.onetomany.OneToManyTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestManualSynchronizationorg.hibernate.test.sql.GeneralTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTesttestHandSQLorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTesttestFiltersWithJoinedSubclassorg.hibernate.test.subclassfilter.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 0) --- End Message --- ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-mysql-testsuite Build Completed With Testsuite Errors]
Thanks. I'll contact you again when 5.0 tests are configured. Steve Ebersole wrote: >AFAIK, yes. In scanning through a lot of the unexpected failures, the >ones I saw were all caused by an issue with handling temp tables in >MySQL, which I am already aware of... > >-Original Message----- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Friday, December 01, 2006 7:15 AM >To: Steve Ebersole >Cc: hibernate-dev@lists.jboss.org >Subject: Re: [Fwd: hibernate-mysql-testsuite Build Completed With >Testsuite Errors] > >I'll create a build against 5.0 but first I need a confirmation about >existing tests. >Are they ok? > >Steve Ebersole wrote: > > > >>Well, I'd much prefer using MySQL 5 as that is now the supported >>production ready line and is the version I test against locally. I >>guess ideally both 4.x and 5.x, if that would be possible, since I am >>sure people will continue using 4.x for quite q while. >> >>If adding or moving to 5.0 is not possible, then this is fine. >> >>-Original Message- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Friday, December 01, 2006 6:58 AM >>To: hibernate-dev@lists.jboss.org; Steve Ebersole >>Subject: [Fwd: hibernate-mysql-testsuite Build Completed With Testsuite >>Errors] >> >>Hi again. >>Please review the results with mysql 4.1.22 (latest 4.1). There are 2 >>tests more passing than with the old one (4.1.10a). >> >>Do the results satisfy you so I can move to the next database or mysql >>should be tunned better? >> >>Thanks, >>Aleksandar >> >> >> >> ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Re: [Fwd: hibernate-mysql-testsuite Build Completed With Testsuite Errors]
I'll create a build against 5.0 but first I need a confirmation about existing tests. Are they ok? Steve Ebersole wrote: >Well, I'd much prefer using MySQL 5 as that is now the supported >production ready line and is the version I test against locally. I >guess ideally both 4.x and 5.x, if that would be possible, since I am >sure people will continue using 4.x for quite q while. > >If adding or moving to 5.0 is not possible, then this is fine. > >-Original Message- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Friday, December 01, 2006 6:58 AM >To: hibernate-dev@lists.jboss.org; Steve Ebersole >Subject: [Fwd: hibernate-mysql-testsuite Build Completed With Testsuite >Errors] > >Hi again. >Please review the results with mysql 4.1.22 (latest 4.1). There are 2 >tests more passing than with the old one (4.1.10a). > >Do the results satisfy you so I can move to the next database or mysql >should be tunned better? > >Thanks, >Aleksandar > > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] [Fwd: hibernate-mysql-testsuite Build Completed With Testsuite Errors]
Hi again. Please review the results with mysql 4.1.22 (latest 4.1). There are 2 tests more passing than with the old one (4.1.10a). Do the results satisfy you so I can move to the next database or mysql should be tunned better? Thanks, Aleksandar --- Begin Message --- View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061201071124 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 12/01/2006 07:11:24Time to build: 34 minutes 49 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (943) Total Errors and Failures: (48)testCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestBooleanHandlingorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateWithWhereExistsSubqueryorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnComponentorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnImplicitJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMammalorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullUnionSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnMappedJoinorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassAbstractRootorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassConcreteSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassLeafSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteWithMetadataWhereFragmentsorg.hibernate.test.hql.BulkManipulationTesttestDeleteRestrictedOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesReverseorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesPositioningorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestWithClauseFailsWithFetchorg.hibernate.test.hql.WithClauseTesttestWithClauseorg.hibernate.test.hql.WithClauseTesttestInterfaceProxiesorg.hibernate.test.interfaceproxy.InterfaceProxyTesttestQueryorg.hibernate.test.legacy.FooBarTesttestOneToOneGeneratororg.hibernate.test.legacy.FooBarTesttestReachabilityorg.hibernate.test.legacy.FooBarTesttestVersionedCollectionsorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestOneToManyLinkTableorg.hibernate.test.onetomany.OneToManyTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestManualSynchronizationorg.hibernate.test.sql.GeneralTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTesttestScalarStoredProcedureorg.hibernate.test.sql.MySQLTesttestParameterHandlingorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTesttestFiltersWithJoinedSubclassorg.hibernate.test.subclassfilter.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2301)10905modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/PersistentClass.javaANN-425 Property not found when defined in a @IdClass and referenced by a @OneToManyANN-499 @IdClass and @ManyToOne leads to repeated column exception10900modifiedepbernard//trunk/Hibernate3/src/org/hibernate/persister/collection/AbstractCollectionPersister.javaHHH-227510897modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/Collection.javaHHH-2274 use ordered collection when manyToManyOrderBy is used10884modifiedhonma//trunk/H
Re: [hibernate-dev] hibernate mysql testsuite
Max Rydahl Andersen wrote: > > As the testsuite was continually failing because of a mysql bug > that is > fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? >>> >>> yes, knowing what that bug is would be beneficial. >>> And regarding the version then Mysql 4.whateveristhelateststable >>> sounds like the best match. >> > > no bug ref still ? :) > There will not be ;) Sorry I've sent a note to Darryl and not to the list. I've lost the ref. I don't have even the error message now so it will be very hard to find it again. The bug is that there get tables created which cannot be dropped because of some temporary files incorrectly created. It is not a problem for now, but could appear in the future breaking any consequent tests. And this is why I think we need a newer version." >>> Mysql 5 is still in beta, correct ? >> >> >> No. 5.0 went GA I guess 3rd Nov 2005. > > > ah - not so long ago then ;) > >> I'd have thought having access to a working SQL server from each >> vendor in each supported version series must be a useful resource >> just to have anyway. If you want pointers on installing/dual homing >> your test box with multiple MySQL servers drop me a mail. > > > I got too many different db installations to count on my box so i got > it covered ;) So which version do you guys prefer and is the fail rate for the mysql tests normal? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate mysql testsuite
I've already sent this, but got no answer. Please take a look at it. Take a look at the hibernate mysql tests: http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite There are much failings. As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Could you suggest which version will best suite your needs (4.1.latest, 5.0.latest)? btw. hibernate can be tested against innodb and myisam. Currently it is tested only against innodb. Is this ok? Thanks, Aleksandar Kostadinov ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate testsuite
Hi Is it possible/easy to create a target in the hibernate's build.xml which cleans the test database as specified in hibernate.properties? This would be very useful for the continuous builds. Thanks, Aleksandar Kostadinov ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate mysql testsuite
Take a look at: http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite There are much failings. As the initial problem as I think was a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Could you suggest which version will best suite your needs (4.1.latest, 5.0.latest)? btw. hibernate can be tested against innodb and myisam. Currently it is tested only against innodb. Is this ok? Thanks, Aleksandar Kostadinov ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
