On Thu, Nov 8, 2018 at 9:45 AM Robert Varga <n...@hq.sk> wrote: > On 08/11/2018 02:09, Jenkins wrote: > > Attention controller-devs, > > > > Autorelease oxygen failed to build sal-distributed-datastore from > controller in build > > 477. Attached is a snippet of the error message related to the > > failure that we were able to automatically parse as well as console > logs. > > > > > > Console Logs: > > > https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-oxygen/477 > > This is the third time Oxygen autorelease has failed on CDS unit tests, > which are (inherently) time-sensitive. Each time it was a different test > and while we can increase timeouts > (https://git.opendaylight.org/gerrit/77597), these tests have been > stable for a long time -- which, coupled with other performance-related > questions cropping up, is leading me to ask: > > What is happening to our build infrastructure lately? >
We haven't really made any changes to infrastructure lately. Main things are just been occasional upgrades to Jenkins and such. Are we sizing the VMs differently? > Nope, we are still running on the same centos7-autorelease-8c-32g VM that we've been using since July https://git.opendaylight.org/gerrit/74305 due to older branches of ODL requiring more resources, and haven't reverted that patch since so if anything we are building on an even larger system for autorelease than we used to need. Can we get a statement from our cloud provider, please? > I've CC'd Mo on this thread. Regards, Thanh
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
