Hi Hideyuki,

This patch looks good to me, but looks like CSIT test is failing on this
patch. Did you run the CSIT-only-boron /CSIT-only-Beryllium test on these
patches ?

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-flow-services-only-beryllium/
https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-flow-services-only-boron/

Shiguru/Hideyuki, I looked at the first test CSIT job
https://jenkins.opendaylight.org/releng/job/openflowplugin-patch-test-boron/12/
: UNSTABLE (skipped)

And it shows 4 failure for the *-only-boron job (
openflowplugin-csit-1node-flow-services-only-boron
<https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-flow-services-only-boron/>[image:
Unstable]#518
<https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-flow-services-only-boron/518/>)
and these flows are related to flow/group operational flow. Can you please
have a look at it and see if these are anyway related to your patch.

Luis, i think none of us have access to trigger these CSIT job against the
patch. I think shiguru and others tried to run test-openflowplugin, but
looks like all the attempt failed (Except the first one) for some reason.
So if we can get result of above two tests, we can merge the patch.

On Thu, Jul 21, 2016 at 3:37 PM, Tai, Hideyuki <[email protected]>
wrote:

> Hi committers of the OpenFlow Plugin project,
>
> Could you review and merge the following patch for the bug 6073?
>
> https://git.opendaylight.org/gerrit/#/c/42213/
>
> We would like to get this change in the Beryllium SR3 which is cut off on
> July 24.
>
> Best Regards,
> Hideyuki Tai
>
> _______________________________________________
> openflowplugin-dev mailing list
> [email protected]
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>



-- 
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to