Nexus crashed this morning and caused autorelease boron to fail it's build. Since I had to restart the autorelease-release-boron job anyway I merged this patch before kicking off the new build. It should be included in:
https://jenkins.opendaylight.org/releng/job/autorelease-release-boron/244/ Regards, Thanh On Wed, Sep 7, 2016 at 2:49 AM, Brady Allen Johnson < [email protected]> wrote: > > An, > > The patch [0] is ready in stable/boron, and I just +2'd it. Can you > arrange to have it merged, please. > > Thanks, > > Brady > > [0] https://git.opendaylight.org/gerrit/#/c/45283/ > > On 06/09/16 18:52, Brady Johnson wrote: > > An, > > Thanks for that, I'll be sure to get the patch merged ASAP. > > Regards, > > Brady > > On Sep 6, 2016 18:30, "An Ho" <[email protected]> wrote: > >> This bug is currently blocking Boron RC3. >> >> As reported by Brady Allen Johnson [1], there is a Boron Blocker Bug for >> SFC related to VPP Renderer integration with Honeycomb. The bug has been >> assigned to colleagues in Intel China with an ETA of 9/7 morning (GMT+1) >> and no known workaround exists for the blocker bug (cannot be retargeted >> for Boron-SR1). Once a patch is verified, can someone from the SFC team >> please +2 the patch. >> >> https://bugs.opendaylight.org/show_bug.cgi?id=6640 SFC VPP Renderer >> can't work with Honeycomb and VPP >> >> Best Regards, >> An Ho >> >> [1] https://lists.opendaylight.org/pipermail/release/2016-Septem >> ber/008128.html >> _______________________________________________ >> 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
