This is probably related to BC 1.61, quoting 1.62 release notes: A performance issue with RSA key pair generation that was introduced in 1.61 has been mostly eliminated. I am not sure it's worth re-sp

Note this means distribution-merge-managed-$stream jobs are not being triggered and hence the distribution has not been refreshed since Friday... Regards, Robert

Hello, ever since 5/31 it seems all merge jobs are marked as unstable due final steps failing, usually around surefire reports: https://jenkins.opendaylight.org/releng/job/netconf-merge-sodium/171/con

Hello Thanh, Ah yes, I did not read up on the web-side of the topic. This is a concern critically important for me. https://bugzilla.mozilla.org/show_bug.cgi?id=366559 offers some insight, eventually

#2​44 27-May-2019 09:46 Hmm... what is the usual achieved rate? Jam0, we've been messing with those numbers last, but I do not remember the specifics... Well, regressions needs to be investigated. On

Hello, it seems our captured logz are no longer getting compressed with .gz: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-3node-clustering-ask-all-neon/247/robot-plugin/

BouncyCastle was upgraded and its karaf wiring changed. Can you SSH to karaf locally? (sorry, don't have a distro handy). Regards, Robert

That is good enough for me :) Thanks, Robert

And yes, Michael's patches are doing the wrong thing by sifting through our source code repositories -- they'd pick up things like CSIT driver models and mdsal-binding-test-model (which supports MD-SA

Actually, we should not be relying on ODL source code repositories to find the models. Models should be extracted from .jars which are part of a built distribution (.zip/.tar.gz) -- hence whatever job

Hello everyone, I ran multipatch builds on https://git.opendaylight.org/gerrit/#/q/topic:mdsal-4.0.1 to validate the upgrade: https://jenkins.opendaylight.org/releng/view/integration/job/integration-m

Thanks for finding that. https://git.opendaylight.org/gerrit/#/c/32070/ provides a clue, esp. pointer to https://wiki.opendaylight.org/view/OpenDaylight_Controller:Netconf:Testtool#Slow_creation_of_de

Hmm... those reports are supposed to be archived, but it seems they are not (not even for verify/merge jobs). @infrastructure, @integration-dev: is this something that got broken along the way? Regard

git repos as storage for binaries is a non-starter, but we do have storage for jenkins minions, etc. and nexus, so this should be workable. Otherwise +1 to the proposal. Regards, Robert

Empty lists are disappearing in Neon: https://lists.opendaylight.org/pipermail/yangtools-dev/2018-September/002308.html, so this is fully expected. Regards, Robert

Yeah, mdsal has not branched yet for Sodium, so Neon stuff is still on master. This is a normal state of affairs for MRI -- we do not branch next development until we need to. Wouldn't it be better to

There does not seem to be anything out of the ordinary from CDS perspective, but there are some OLFE/validation errors. Can someone from the OFP team take a look, please? Thanks, Robert

Hello Alexis, looks good. karaf4-parent is not the right place, as they are inherently CDS-aware. I think the best option would be to provide them through a separate artifact from int/dist. Regards, R

Alright, we can ditch the builder debugs, as everything there works as it is supposed to. The reason for non-removal of the links is captured in https://logs.opendaylight.org/sandbox/vex-yul-odl-jenki

Not sure... if we have messed up accounding (below), we may end up reporting things out of whack. Thanks, this actually provides a lead: everything works with normal transaction chains, yet breaks dow