I'm looking into it. Seems like when the tests finished, the cache is cleared,
which sometimes can lead to suspect exceptions.
Not too serious. I'll sort out asap.
On Nov 6, 2012, at 4:24 AM, Strong Liu wrote:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/hibernate-core-master/522/test
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/hibernate-core-master/522/testReport/junit/
could someone take a look?
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
___
hibernate-dev mailing list
hibernate-dev@lists.
If you can reproduce this easily, enable TRACE on org.infinispan and
org.jgroups and send me the logs.
On Aug 8, 2012, at 7:26 AM, Strong Liu wrote:
> I'm seeing lots of infinispan test failures, I guess mostly relate to the
> jgroups, propbaly an environment issue, wondering anyone has a worka
I'm seeing lots of infinispan test failures, I guess mostly relate to the
jgroups, propbaly an environment issue, wondering anyone has a workaround?
java.lang.IllegalStateException: Cache at address server-15967 had 3 members;
expecting 2. Members were (server-64288, server-15967, server-6121)
Ok.
If the infinispan testsuite takes forever, please send some thread dumps.
If you get failures, please indicate the failures.
If you get failures often enough that you can easily replicate, add TRACE
logging to org.infinispan and org.hibernate.cache.infinispan packages and send
me the logs.
Its just more of the same "sometimes they pass, sometimes they fail".
On Tue 13 Mar 2012 03:44:25 AM CDT, Galder Zamarreño wrote:
> Do you have more info on these failures?
>
> On Mar 9, 2012, at 7:01 PM, Steve Ebersole wrote:
>
>> Yaay! It ony took slightly over 5 minutes today. But of course:
Do you have more info on these failures?
On Mar 9, 2012, at 7:01 PM, Steve Ebersole wrote:
> Yaay! It ony took slightly over 5 minutes today. But of course:
>
>> Building > :hibernate-infinispan:test > Resolving dependencies
>> ':hibernate-infinispan:test:hibernate-infinispan:test
> Test
> o
Yaay! It ony took slightly over 5 minutes today. But of course:
> Building > :hibernate-infinispan:test > Resolving dependencies
> ':hibernate-infinispan:test:hibernate-infinispan:test
Test
org.hibernate.test.cache.infinispan.entity.InvalidatedTransactionalTestCase
FAILED
Test org.hibernate.t
Luckily you get to decide to follow the company line and use inferior
tools as part of your project.
Considering that part works everywhere I find it funny that you can
chalk my issue up to env but this has to be a "gradle/ivy bug" lol.
There is also a far easier syntax for how you are trying t
No idea why, the JAR is there - maybe a Gradle/Ivy issue?
https://repository.jboss.org/nexus/content/groups/public/org/infinispan/infinispan-core/5.1.2.CR1/infinispan-core-5.1.2.CR1-tests.jar
I don't get this issue in my own env btw.
On Mar 8, 2012, at 2:19 AM, Strong Liu wrote:
> btw ci fails d
On Mar 8, 2012, at 4:46 PM, Strong Liu wrote:
>
> On Mar 8, 2012, at 6:48 PM, Sanne Grinovero wrote:
>
>> Hi,
>> I found the same files in my workspace as left over from and older
>> build, but deleted them and tried new builds several times, they don't
>> seem to be re-created anymore?
>> Coul
On Mar 8, 2012, at 10:48 AM, Sanne Grinovero wrote:
> Hi,
> I found the same files in my workspace as left over from and older
> build, but deleted them and tried new builds several times, they don't
> seem to be re-created anymore?
> Could anyone confirm (after cleaning them up) that it's still
Not Infinispan, but JBoss Transactions.
On Mar 8, 2012, at 9:15 AM, Hardy Ferentschik wrote:
> This used to happen in Search as well, but is gone now (I think). Must be in
> Infinispan config thing.
> Sanne probably knows :-)
>
> --Hardy
>
>
> On Mar 8, 2012, at 2:53 AM, Steve Ebersole wrote
My bad, I'll do that right away. CR1 was released just 3 days before FINAL, so
it's pretty stable already.
On Mar 8, 2012, at 2:56 AM, Steve Ebersole wrote:
> Hmm, I did not have problems resolving artifacts, but I just noticed
> this CR... we really need to not be upgrading to CR releases of
My build, including running tests, took:
Total time: 2 mins 53.136 secs
So, I'd say it's some env issue, maybe UDP traffic generated by the cluster
tests getting stuck somewhere?
Btw, I did improve the speed of these tests hugely a few months ago by
switching to an in-memory discovery protocol
Steve,
Just built it and I see no such folders in my env:
https://gist.github.com/2005857
Maybe these are old folders that were lying around?
They look to be JBoss Transactions related.
Cheers,
On Mar 8, 2012, at 1:53 AM, Steve Ebersole wrote:
> Running the hibernate-infinispan tests I am see
On Mar 8, 2012, at 6:48 PM, Sanne Grinovero wrote:
> Hi,
> I found the same files in my workspace as left over from and older
> build, but deleted them and tried new builds several times, they don't
> seem to be re-created anymore?
> Could anyone confirm (after cleaning them up) that it's still a
Well I recently just "upgraded" to Fedora 14 so that may very well have
something to do with it. The hibernate-infinispan tests always ran slow,
but this 56 minutes number is a whole new level of frustration ;)
st...@hibernate.org
http://hibernate.org
On Mar 8, 2012 9:54 AM, "Sanne Grinovero" wr
11 minutes?!?! I had to kill the one last night and just disable those
tests for the release. This morning I let it run. 56 minutes. Yep
56! And thats solely for running the hibernate-infinispan tests.
Everything else was built already.
[steve@apollo hibernate-infinispan]$ gradle clean t
On Mar 7, 2012, at 8:19 PM, Strong Liu wrote:
> On Mar 8, 2012, at 10:04 AM, Steve Ebersole wrote:
>
>> Speaking of which, is everyone else seeing tests in
>> hibernate-infinispan taking many many minutes to run?
>
>
> yes, it reallly takes some time
I've been seeing that for a while, too.
On 8 March 2012 13:02, Steve Ebersole wrote:
> I saw a file show up in one of them during the runs. It was deleted
> afterwards. As to whether or not they show up ever again if I manually
> delete them... dunno. But I'd also like to know the who/why/whats
> about them as well...
Those are reco
I saw a file show up in one of them during the runs. It was deleted
afterwards. As to whether or not they show up ever again if I manually
delete them... dunno. But I'd also like to know the who/why/whats
about them as well...
11 minutes is less then what I saw. This is not a "quick turnaro
On Mar 8, 2012, at 11:48 AM, Sanne Grinovero wrote:
> I found the same files in my workspace as left over from and older
> build, but deleted them and tried new builds several times, they don't
> seem to be re-created anymore?
> Could anyone confirm (after cleaning them up) that it's still a
> pr
Hi,
I found the same files in my workspace as left over from and older
build, but deleted them and tried new builds several times, they don't
seem to be re-created anymore?
Could anyone confirm (after cleaning them up) that it's still a
problem, as I can't..
On the build issues, I had to rebuild a
Hi,
it just took 5 attempts to build everything :-(
The first two times I got errors due to unresolved dependencies (first time
some docbook stuff, then Infinispan).
In both cases the problem went away by restarting the build.
The third time around I got a test failure in
org.hibernate.test.an
This used to happen in Search as well, but is gone now (I think). Must be in
Infinispan config thing.
Sanne probably knows :-)
--Hardy
On Mar 8, 2012, at 2:53 AM, Steve Ebersole wrote:
> Running the hibernate-infinispan tests I am seeing 2 output directories
> showing up in the hibernate-inf
Hmm, I did not have problems resolving artifacts, but I just noticed
this CR... we really need to not be upgrading to CR releases of
dependencies as part of a point release. Sigh
On Wed 07 Mar 2012 08:19:55 PM CST, Strong Liu wrote:
> btw ci fails due to
>
> 08:23:54.474 [ERROR] [org.gradle.Bui
btw ci fails due to
08:23:54.474 [ERROR] [org.gradle.BuildExceptionReporter] Could not resolve all
dependencies for configuration ':hibernate-infinispan:testCompile'.
08:23:54.478 [ERROR] [org.gradle.BuildExceptionReporter] > Artifact
'org.infinispan:infinispan-core:5.1.2.CR1:tests@jar' not fou
Speaking of which, is everyone else seeing tests in
hibernate-infinispan taking many many minutes to run?
On Wed 07 Mar 2012 07:53:42 PM CST, Steve Ebersole wrote:
> Running the hibernate-infinispan tests I am seeing 2 output
> directories showing up in the hibernate-infinispan directory (aka, n
Running the hibernate-infinispan tests I am seeing 2 output directories
showing up in the hibernate-infinispan directory (aka, not
hibernate-infinispan/target/...). Namely, I see
hibernate-infinispan/ObjectStore and
hibernate-infinispan/PutObjectStoreDirHere. Anyone know how/if we can
change
30 matches
Mail list logo
