Claudio, On Thu, Jan 25, 2018 at 4:52 PM, Claudio David Gasparini < claudio.gaspar...@pantheon.tech> wrote:
> Same issue has been observed under bgp test. > I had a look at https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-nitrogen/368/bgpcep/integration-tests/target/surefire-reports/org.opendaylight.protocol.integration.pcep.PcepRpcServicesRoutingTest-output.txt.gz and it shows no errors before the "org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting for service org.ops4j.pax.exam.ProbeInvokerFactory", after which it is still initializing stuff... assuming that this works locally, my suspicion is that perhaps on jenkins when things go slow we need to make the IT with Pax Exam a bit more patient? I'm wondering if increasing those timeout attributes on your IT's (and it's parent class/es) @org.ops4j.pax.exam.util.Filter annotations could help... > *Claudio David Gasparini* > > Senior Software Engineer > > > *PANTHEON* *technologies s.r.o.* > > Mlynské Nivy 56, 821 05 Bratislava > <https://maps.google.com/?q=Mlynsk%C3%A9+Nivy+56,+821+05+Bratislava%0D+%0D+Slovakia&entry=gmail&source=g> > > Slovakia > <https://maps.google.com/?q=Mlynsk%C3%A9+Nivy+56,+821+05+Bratislava%0D+%0D+Slovakia&entry=gmail&source=g> > > Tel / +421 220 665 111 > > > > *MAIL **/ *claudio.gaspar...@pantheon.tech > > *WEB **/* https://pantheon.tech <https://pantheon.tech/> > <https://pantheon.tech/> > > > [0] https://jenkins.opendaylight.org/releng/job/ > autorelease-release-nitrogen/368/ > > [1] https://logs.opendaylight.org/releng/vex-yul-odl- > jenkins-1/autorelease-release-nitrogen/368 > > ------------------------------ > *From:* Robert Varga <n...@hq.sk> > *Sent:* Wednesday, January 24, 2018 8:39:29 PM > *To:* Michael Vorburger; controller-dev > *Subject:* Re: [controller-dev] DistributedDataStoreRemotingIntegrationTest > failures > > On 24/01/18 18:58, Michael Vorburger wrote: > > also sal-binding-it is flaky, not sure if related, see > > https://git.opendaylight.org/gerrit/#/c/67266/ ... we can always > > "recheck", of course - but we shouldn't have to, ideally. > > > Error in initialization script: > /w/workspace/controller-maven-verify-oxygen-mvn33-openjdk8/ > opendaylight/md-sal/sal-binding-it/target/exam/890e2a1b-7fae-4cf5-936b- > 5da9ed380f81/etc/shell.init.script: > String index out of range: 0 > karaf@root()> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, > Time elapsed: 209.215 s <<< FAILURE! - in > org.opendaylight.controller.test.sal.binding.it.DataServiceIT > [ERROR] > test(org.opendaylight.controller.test.sal.binding.it.DataServiceIT) > Time elapsed: 209.215 s <<< ERROR! > org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting > for service org.ops4j.pax.exam.ProbeInvoker > > looks like a pax-exam sensibility. I don't know why the verify job has > not preserved any evidence -- maybe start there? > > Bye, > Robert > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
