Given that Neon still hasn't started we can give it some grace to stabilize however once we formally started it there should not be any transient failures which we don't understand the root cause. This is our only way to stabilize things.
Thanks. On Mon, Aug 27, 2018 at 12:59 PM Brady Johnson <[email protected]> wrote: > I tried to reproduce this compilation failure locally, and wasnt able to. > Let see if its just a transient failure. > > Regards, > > *Brady Johnson* > [email protected] > > > > > > On Thu, Aug 23, 2018 at 4:39 AM Jenkins < > [email protected]> wrote: > >> Attention sfc-devs, >> >> Autorelease neon failed to build sfc-provider from sfc in build >> 16. 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-neon/16 >> >> Jenkins Build: >> https://jenkins.opendaylight.org/releng/job/autorelease-release-neon/16/ >> >> Please review and provide an ETA on when a fix will be available. >> >> Thanks, >> ODL releng/autorelease team >> >> _______________________________________________ >> sfc-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/sfc-dev >> > _______________________________________________ > release mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/release >
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
