December 2006 - hibernate-dev - Jboss List Archives

Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]

by Aleksandar Kostadinov

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:akostadinov@jboss.org] >Sent: Sunday, December 03, 2006 6:18 AM >To: hibernate-dev(a)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. > >

17 years, 5 months

1
0
0 / 0

Testsuite for new SQL dialect

by Thomas Jäckel

Hello Everybody, I have started to implement a new SQL dialect (Pervasive SQL). I wanted to verify my implementation with the hibernate junittests. Some tests do fail beacause they generate sql operations on tables that do not exist and are not tried to create either. i.e.: Testsuite: org.hibernate.test.array.ArrayTest Testsuite: org.hibernate.test.bidi.AuctionTest org.hibernate.test.bytecode.cglib.InvocationTargetExceptionTest ... Did I oversee something? Have the tables to be created manually? What could be an other reason for the not created tables? Is the reason to find in the dialect class? I have activated the hibernate SQL output option, but there is not a create statement in the log. Version: hibernate 3.2.1 Thanks for any hint. Thomas Jäckel -- OPC cardsystems GmbH Tel. +49 2203 459 877 Mobil: +49 176 12560002 Zentrale: +49 651 8408 0

17 years, 5 months

1
0
0 / 0

hibernate-oracle10-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

hibernate-mysql-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

hibernate-mysql50-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

hibernate-hsqldb-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

hibernate-mysql-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

hibernate-mysql50-testsuite Build Completed With Testsuite Errors

by qa＠jboss.com

17 years, 5 months

1
0
0 / 0

RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

by Steve Ebersole

Um, perhaps if you are going to ask me to do something you could can the attitude? Seems like a basic requirement to me... As far as the box hosting the runs, I did not realize I had presumed anything. The point was simply that it seems silly to me to invest a lot of effort to script this when this could simply be hard-coded info since they all run on the same exact env. Is it as easy as a couple of printlns? I don't know (again see my qualification that I do not know CruiseControl). BTW, nothing is a lot of effort when someone else is doing all the work ;) So Max was not aware that MySQL 5.0 had gone GA. How exactly would us making these things you ask for more accessible in our testsuite results have changed that? I am simply telling Aleksandar that if this takes a lot of effort that I would much prefer him instead continuing to focus his efforts on getting more database coverage up and running. You don't agree with that? Great! Let us know when you have your hosted Hibernate test suite up and running; then you can call the shots. But to me I am more interested in the coverage; I can live with 4 clicks to get this other info in the meantime. -----Original Message----- From: Darryl Miles [mailto:darryl-mailinglists@netbauds.net] Sent: Monday, December 04, 2006 11:40 AM To: Steve Ebersole Cc: Aleksandar Kostadinov; hibernate-dev(a)lists.jboss.org Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors] Steve Ebersole wrote: > I am not really familiar with CruiseControl, so what exactly do you mean > by "emit"? emit in this case means make it clearly visible at first glance which JDK, Host, JDBC Driver and SQL Server version are being used for the test case run. That seems like a pretty basic requirement to me. > AFAIK, the same box hosts the various runs, correct? So unless there > are plans to change that, a lot of effort here seems silly. This presumes everybody with an interest in the test results generated from that box is also kept in the loop with all future changes and upgrades of that box. This presumes that the person responsible for maintaining the testing box understands all the implications of interactions with the various versions of the components used in the tests. I'm surprised you think what should amount to a couple of out.println() statements is "a lot of effort". For example Max wasn't aware 5.0 has gone GA, well it if was clear from looking at the test summary what was actually being tested someone with a better knowledge could have pointed something like that out. I don't expect everyone to know everything about everything and I also don't expect everyone to go digging at the sight of every test failure. So if something can be done to make the test results a more accurate picture of where things stand is a good thing by me. YMMV > (these are from my local setup). Great, but of little relevance to the daily testing emailed to the devel list. Darryl

17 years, 5 months

2
1
0 / 0

RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

by Steve Ebersole

I am not really familiar with CruiseControl, so what exactly do you mean by "emit"? AFAIK, the same box hosts the various runs, correct? So unless there are plans to change that, a lot of effort here seems silly. As far as the extra JDBC metadata, the JDBC driver is *supposed* to make this info available via the DatabaseMetadata; be warned not all Connection impls do a good job of this. At any rate, Hibernate logs this info during SessionFactory initialization (in the testsuite's hibernate.log output): 10:57:31,981 INFO SettingsFactory:81 - RDBMS: MySQL, version: 5.0.27-community-nt 10:57:31,981 INFO SettingsFactory:82 - JDBC driver: MySQL-AB JDBC Driver, version: mysql-connector-java-5.0.4 ( $Date: 2006-10-19 17:47:48 +0200 (Thu, 19 Oct 2006) $, $Revision: 5908 $ ) 1 (these are from my local setup). -----Original Message----- From: hibernate-dev-bounces(a)lists.jboss.org [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Darryl Miles Sent: Monday, December 04, 2006 9:54 AM To: Aleksandar Kostadinov Cc: hibernate-dev(a)lists.jboss.org Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors] 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

17 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev December 2006