I am watching a build I just kicked off right now in the ui console and
the sticking point seems to actually be compiling the test classes
(unless I am mis-understanding the console).
The step where the build hung (just before dieing) was:
:hibernate-core:testClasses
I have to see what all testClasses involves. Actual test source
compilation was already completed earlier.
On Thu 25 Apr 2013 03:32:30 PM CDT, Sanne Grinovero wrote:
I think it's an environment problem of our CI, I yet have to
understand what this message means but while using less memory could
be a valid workaround, I still suspect the problem is not in
Hibernate's code. Sorry this is going to be a bit slow I need to get a
RH subscription to get proper support.. Suggestion from Linux experts
welcome in the meantime: I've never seen such an error before.
Sanne
On 25 Apr 2013 20:53, "Steve Ebersole" <steve(a)hibernate.org
<mailto:steve@hibernate.org>> wrote:
As far as I can tell there are no tests leaving the SessionFactory
open in hibernate-core. I have not tested yet with the other
modules, but from what I can see the CI builds fail at the point
trying to run these tests.
Essentially I added a hook in CustomRunner (in
AfterClassCallbackHandler to be precise) to check the
SessionFactoryRegistry to make sure there are no still registered
SessionFactories after a test class is done. If there are, it
logs a message and clears the SessionFactoryRegistry. This is
simplistic as we still have other resources that need to be
checked (ServiceRegistries are used independently from
SessionFactory quite a bit).
This was after I got all tests indicated by Strong to extend
BaseUnitTestCase that did not previously. I did have problems
with
org.hibernate.metamodel.__source.annotations.xml.mocker.__AbstractMockerTest
and subclasses. Having it extend BaseUnitTestCase with that
functionality led to assertion failures in 3 tests:
BasicMockerTest.__testEntityWithEntityMappingsCo__nfiguration
OverrideTest.__testPersistenceUnitDefaultsCas__cadePersistInAnnotation
OverrideTest.__testPersistenceUnitMetadataMet__adataComplete
Which is odd, because those tests don't even deal with a
SessionFactory.
As for checking that created ServiceRegistry instances get cleaned
up, not sure how we can check that.
Another thing we should do is to exclude the metamodel tests
currently on master. After that, I am out of ideas...
On Thu 25 Apr 2013 05:28:35 AM CDT, Sanne Grinovero wrote:
On 25 April 2013 09:04, Strong Liu <stliu(a)hibernate.org
<mailto:stliu@hibernate.org>> wrote:
Sanne,
is it possible that you give me ssh access to the ci server?
Sure; I'm adding Strong, if anyone else wants root access just
send me
your public key using your redhat account.
Cheers,
Sanne