+1 On 28 August 2010 10:49, zoe slattery <[email protected]> wrote: > Hi Joe - I've worked through everything successfully and didn't hit it - > but if it's intermittent that isn't surprising. I raised > https://issues.apache.org/jira/browse/ARIES-391 in case other people hit it. > > Zoė >> >> Thanks Zoe. I've rebuilt aries *jpa* probably 10 more times now and I was >> just about to post that I couldn't recreate the failure when I suddenly hit >> it once again. This time it was slightly different in that we were waiting >> for the PersistenceContextProvider. >> >> Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 47.464 sec >> <<< FAILURE! >> testComplexContextQuiesce >> [equinox/3.5.0](org.apache.aries.jpa.quiesce.itest.QuiesceJPATest) Time >> elapsed: 4.259 sec <<< ERROR! >> java.lang.RuntimeException: Gave up waiting for service >> (objectClass=org.apache.aries.jpa.container.context.PersistenceContextProvider) >> at >> org.apache.aries.jpa.quiesce.itest.QuiesceJPATest.getOsgiService(QuiesceJPATest.java:695) >> at >> org.apache.aries.jpa.quiesce.itest.QuiesceJPATest.getOsgiService(QuiesceJPATest.java:668) >> at >> org.apache.aries.jpa.quiesce.itest.QuiesceJPATest.getOsgiService(QuiesceJPATest.java:664) >> at >> org.apache.aries.jpa.quiesce.itest.QuiesceJPATest.testComplexContextQuiesce(QuiesceJPATest.java:176) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke(CallableTestMethodImpl.java:134) >> at >> org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call(CallableTestMethodImpl.java:101) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> <snip/> >> >> However, given that it seems fairly sporadic (and even then may not be a >> real problem) I'm of the opinion this should not stop the vote. >> >> Joe >> >> On 8/27/10 3:01 PM, zoe slattery wrote: >>> >>> Hi Joe - I think it's definitely worth raising this. >>> >>> I didn't see it (yet), but I'm on a second run through after realising >>> that I hadn't deleted everything in my local maven repos. I'll let you >>> know how it goes. >>>> >>>> Well, I don't think this is real problem but I thought I should >>>> mention it in case others see similar results and it begins to become >>>> a pattern. >>>> >>>> I had a difficult time building quiesce this time around. I first hit >>>> a service timeout in QuieseJPATest testComplexUnitQuiesce waiting for >>>> the EntityManagerFactory service. I hit service timeouts from time to >>>> time in the tests while building (usually in blueprint) - so I wasn't >>>> too surprised when I hit the first one. >>>> >>>> However, I then hit a second service timeout on my next attempt to >>>> build quiesce - this time in QuieseJPATest testSimpleUnitQuiesce. Both >>>> of these timeouts were with hit pretty quickly - the first after just >>>> 3.709 sec elapsed time and the second after just 4.229 sec. >>>> >>>> I was finally able to build quiesce with tests passing on the third >>>> attempt. >>>> >>>> So, why the note? >>>> 1) I was surprised by hitting these service timeouts in quiesce (I >>>> usually hit them in blueprint). >>>> 2) I was surprised to hit them twice in a row. >>>> 3) I was surprised to hit them with such a small elapsed time on the >>>> tests that failed. >>>> 4) It was odd that I hit these failures on this vote but didn't see >>>> them on any of the previous votes. Perhaps one of the earlier changes >>>> surfaced a new issue and I was just lucky on my earlier attempts? >>>> >>>> Joe >>>> >>>> On 8/27/10 12:39 PM, zoe slattery wrote: >>>>> >>>>> Starting a discussion thread, although I _really_ hope that there is >>>>> nothing to say :-) >>>>> >>>>> Zoė >>>>> >>>> >>> >>> >> >> > >
-- Alasdair Nottingham [email protected]
