>> If I understand it correctly, VPP project is already
>> not supporting vpp_api_test anymore;
>> and it has not been deleted just because
>> CSIT still depends on it.
>> When CSIT finishes migrating to PAPI, VAT is going to be removed.
>
> VAT is still “supported”, to the extent it ever was.
> T
Vratko,
> If I understand it correctly, VPP project is already
> not supporting vpp_api_test anymore;
> and it has not been deleted just because
> CSIT still depends on it.
> When CSIT finishes migrating to PAPI, VAT is going to be removed.
VAT is still “supported”, to the extent it ever was.
The
: Paul Vinciguerra ; Matthew Smith
; csit-...@lists.fd.io; vpp-dev
Cc: NPG-PRC-SW FDIO Project team ; Liu,
Yu Y
Subject: Re: [vpp-dev] sw_interface_dump changes
Hi csit-dev and Paul,
This Changes also caused CSIT test fails, Should it be fixed in vpp_api_test
?
[cid:image002.jpg
@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Paul
Vinciguerra
Sent: Friday, April 19, 2019 5:51 AM
To: Matthew Smith
Cc: vpp-dev
Subject: Re: [vpp-dev] sw_interface_dump changes
Hi Matt.
If you look at https://gerrit.fd.io/r/#/c/18693/5/test/vpp_papi_provider.py,
the field was set to default
Hi Matt.
If you look at https://gerrit.fd.io/r/#/c/18693/5/test/vpp_papi_provider.py,
the field was set to default to ~0 for the python client. When I made the
change, I chose to do it this way to make the api fall more in line with
other calls such as l2_interface_efp_filter and
sw_interface_rx_
Hi,
It looks like in https://gerrit.fd.io/r/#/c/18693/ the message format and
handler for sw_interface_dump changed in a backwards-incompatible way. It's
not too difficult to correct for, but it seems like any API clients that
used this call might be broken. Some code that I maintain that connects
