View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061205225614
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/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061205224637
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061205221846
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/
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log2006120522
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:106: The following error occurred while executing this line: /home/cruisecontrol/work
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061205170419
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/
No, not really
-Original Message-
From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 05, 2006 2:56 PM
To: Steve Ebersole
Cc: Darryl Miles; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build
CompletedWith Testsuite
2005 introduces the snapshot isolation level (their name for their MVCC
implementation). 2000 and earlier were plagued by deadlock issues. I
do not know of an easy way around that besides "protecting" those tests
individually via the "skipping" mechanism. I do not have the time to do
that right
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 d
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
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 Ex
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 singl
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 t
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.hibern
13 matches
Mail list logo
