View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060610012532
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:100: The following error occurred while executing this line: /home/cruisecontrol/work
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20060609222520
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 06/09/2006 22:25:20Time to build:
Unit Tests: (0) Total Errors and Failures
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-timesten-testsuite?log=log20060609215952
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:93: The following error occurred while executing this line: /home/cruisecontrol/work/
Still not able to reproduce this...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Friday, June 09, 2006 9:44 AM
To: Hibernate development
Subject: Re: [Hibernate] Query failing
I'll take a look. That code block should only actually
>> The day you write a (needed and usefull!) unittest that is not possible
>> in our current setup then lets talk ;)
>
> I've already created patch with couple testcases using same package
> layout
> on purpose.
ok.
>> No reason to change what just works.
>
> reasons: every time the developer
hibernate-annotations-3.2.0.CR1.tar.gz
hibernate-entitymanager-3.2.0.CR1.tar.gz
hibernate-3.2.0.cr2.tar.gz
Guess the method is missing because some are CR1 and some CR2? Those
are the only files on sourceforge to download Thoughts?
Error:
1) testOne(com.test.HibernateEJB3TestSuite)java.lang.
You’re right. We should never have “expected
failure” type tests in a test suite so that we can get back to things we
know we want to fix. That is so crazy; what are we thinking here…
And as for a projects choice of how to define
tests impacting that projects credibility in *your
proj
On Jun 9, 2006, at 6:07 PM, Szczepan Faber wrote:
> Whatever you say, the failing tests / unreasonable test packaging
> just impact the project credibility.
This is the most bizarre thing I've heard in quite a while...
___
hibernate-devel mailing l
> The day you write a (needed and usefull!) unittest that is not possible> in our current setup then lets talk ;)I've already created patch with couple testcases using same package layout on purpose.
> No reason to change what just works.reasons: every time the developer cannot unit test non-public
I'll take a look. That code block should only actually be executing on
"dot structures", which an alias is definitely not...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Friday, June 09, 2006 9:21 AM
To: Emmanuel Bernard
Cc: H
which test is this ? Trying to reproduce it here but no luck.
/max
>
>> But it *is* working if item the alias is renamed i.
>
> yes, because you don't have a class named org.hibernate.ejb.test.i
>
> Note, i can't see why it actually tries to load
> org.hibernate.ejb.test.item and not just item.
>
On Fri, 09 Jun 2006 16:16:44 +0200, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
> But it *is* working if item the alias is renamed i.
yes, because you don't have a class named org.hibernate.ejb.test.i
Note, i can't see why it actually tries to load
org.hibernate.ejb.test.item and not just it
But it *is* working if item the alias is renamed i.
Max Rydahl Andersen wrote:
>
> > No, this is a pure Hibernate EntityManager test, it has nothing to do
> > with app servers.
>
> ah - i didn't see that getConstantValue thingy.
> that error is because of terrible windows that forces the classloa
the fix is either to add an extra catch or somehow improve the parser so it
doesn't try to resolve a classname out of an alias.
/max
>> No, this is a pure Hibernate EntityManager test, it has nothing to do
>> with app servers.
>
> ah - i didn't see that getConstantValue thingy.
> that error is b
> No, this is a pure Hibernate EntityManager test, it has nothing to do
> with app servers.
ah - i didn't see that getConstantValue thingy.
that error is because of terrible windows that forces the classloaders
to have case ignored for lookups ;)
/max
> Max Rydahl Andersen wrote:
>>
>> I have
No, this is a pure Hibernate EntityManager test, it has nothing to do
with app servers.
Max Rydahl Andersen wrote:
>
> I have seen similar NoClassDef when dealing with classloaders in eclipse.
>
> It looks like the current context thread might not be behaving as it
> should ?
> Does this happen
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060609050821
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:100: The following error occurred while executing this line: /home/cruisecontrol/work
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060609045819
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:86: The following error occurred while executing this line: /home/cruisecontrol/work/sc
I have seen similar NoClassDef when dealing with classloaders in eclipse.
It looks like the current context thread might not be behaving as it
should ?
Does this happen only under GlassFish or ?
(but weird that changing the alias makes a difference?)
/max
> Steve,
> JPA compliance + the lite
> b) But what's the reason of making surprising test subpackage (I've never
> seen something like that)? You can still have integration/acceptance test
> cases in 'normal' package or even in different source folder.
> Unreasonable
> subpackage makes it hard to write real unit test, you cannot te
20 matches
Mail list logo
