Quoting Jon Loeliger (2017-11-10 23:11:36)
>First, this is draconian for no really good reason. Second, it should be
>fixed. Third, I would do that except I am stupid and need a clue where
>or how to fix this situation so the tests are less draconian. (Can we
>get a "less than 0
Chris,
On Fri, Nov 10, 2017 at 8:27 PM, Luke, Chris wrote:
> If you’re wondering where the tests are:
>
>
>
> $ ls test/*acl*
>
> test/test_acl_plugin_conns.py test/test_acl_plugin_macip.py
>
> test/test_acl_plugin_l2l3.py test/test_acl_plugin.py
>
Ah, excellent!
> Chris.
>
Thanks!
jdl
_
: Re: [vpp-dev] ACL Build/Test Issues
On Fri, Nov 10, 2017 at 5:54 PM, Andrew Yourtchenko
mailto:ayour...@gmail.com>> wrote:
Hi Jon,
On 10 Nov 2017, at 23:11, Jon Loeliger
mailto:j...@netgate.com>> wrote:
Folks,
Every error from the ACL implementation is -1. Generically bad.
Withou
On Fri, Nov 10, 2017 at 5:54 PM, Andrew Yourtchenko
wrote:
> Hi Jon,
>
> On 10 Nov 2017, at 23:11, Jon Loeliger wrote:
>
> Folks,
>
> Every error from the ACL implementation is -1. Generically bad.
> Without regard for what might be more useful to an upper-layer UI.
>
>
> When we discussed with
Hi Jon,
> On 10 Nov 2017, at 23:11, Jon Loeliger wrote:
>
> Folks,
>
> Every error from the ACL implementation is -1. Generically bad.
> Without regard for what might be more useful to an upper-layer UI.
When we discussed with the openstack folks the way they are treating errors was
all as c
