Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

Great job you both :) > On Mar 3, 2017, at 12:56 PM, Thanh Ha wrote: > > Credit should go to Anil Belur as he did the majority of the implementation. > :) > > Thanh > > > On Fri, Mar 3, 2017 at 3:16 PM, Luis Gomez >

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

Credit should go to Anil Belur as he did the majority of the implementation. :) Thanh On Fri, Mar 3, 2017 at 3:16 PM, Luis Gomez wrote: > This is awesome Thahn, now I see how useful is the automatic message you > implemented. > > On Mar 3, 2017, at 7:51 AM, Thanh Ha

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

This is awesome Thahn, now I see how useful is the automatic message you implemented. > On Mar 3, 2017, at 7:51 AM, Thanh Ha wrote: > > On Fri, Mar 3, 2017 at 5:30 AM, Brady Allen Johnson >

[sfc-dev] Way forward with the 2 MAC Chaining solutions

I had a meeting today with the folks from the 2 different MAC Chaining solutions, and here is the way forward we agreed upon: 1. Rafael will prepare a patch with just the YANG model changes. 2. Brady will do the necessary to officially get the API change merged now that we've passed the

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

On Fri, Mar 3, 2017 at 5:30 AM, Brady Allen Johnson < brady.allen.john...@ericsson.com> wrote: > I just cherry-picked the change to stable/beryllium, and will merge when > ready. > Thanks, would be good to not get random failures since Jenkins will now automatically email the mailing list when a

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

Diego, Nice catch! I couldnt reproduce it, but luckily you recognized the issue. I just cherry-picked the change to stable/beryllium, and will merge when ready. Regards, Brady -Original Message- From: Diego Jesus Granados Lopez

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

Hi all, This is SFC BUG 6613 [1] , already fixed [2] in Carbon and Boron, but not in Berilium. If not backported it can break the build randomly, as it was seen here. Can somebody backport? [1] https://bugs.opendaylight.org/show_bug.cgi?id=6613 [2]

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

I tried this locally, and am not able to reproduce the failure. $ git status On branch stable/beryllium ... --- T E S T S --- Running org.opendaylight.sfc.util.openflow.SfcOpenflowUtilsTest

Re: [sfc-dev] [release] Autorelease beryllium failed to build sfc-openflow-utils

Hi Thanh, I am looking at it. Regards, David Suárez. On jue, 2017-03-02 at 23:20 -0500, Thanh Ha wrote: > Adding sfc-dev. > > Thanh > > On Thu, Mar 2, 2017 at 10:12 PM, Jenkins ght.org> wrote: > > Attention OpenDaylight-devs, > > > > Autorelease beryllium