I don't think we need a re-spin, since it's just a unit test change.
I'm not super sure it made sense to merge this, since we're about to
disable Oxygen jobs, but it also shouldn't be a big problem.
Thanks,
Daniel
On Mon, Dec 10, 2018 at 5:12 PM Jamo Luhrsen wrote:
> wait, we merged a new oxyg
On Fri, Jul 20, 2018 at 10:36 AM Thanh Ha
wrote:
> On Fri, Jul 20, 2018 at 10:01 AM Tom Pantelis
> wrote:
>
>> On Fri, Jul 20, 2018 at 4:48 AM, Anil Belur
>> wrote:
>>
>>> On Fri, Jul 20, 2018 at 11:12 AM Jenkins <
>>> jenkins-dontre...@opendaylight.org> wrote:
>>>
Attention controller-dev
Some test related to persistence timed out after three seconds?
Anything we can do about this? Even if it's "random"/"intermittent" I think
we need to start taking those types of failures very seriously, as we seem
to have so many "sporadic" failures we're extremely likely to hit one of
them in a
Is this the relevant error?
[ERROR]
test(org.opendaylight.controller.test.sal.binding.it.DataServiceIT) Time
elapsed: 195.804 s <<< ERROR!
org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting for
service org.ops4j.pax.exam.ProbeInvoker
Anything we can do about it?
Thanks,
Dan
Hey Muthu,
Yes, I think you should take a look at the systemd configuration we ship in
ODL's packages. As far as I know it does a good job of
starting/stopping/restarting ODL's service.
https://git.opendaylight.org/gerrit/gitweb?p=integration/packaging.git;a=blob;f=packages/rpm/unitfiles/opendayl