Describe the contribution
The "bplib_generic_bundle_ingress()" function was not correctly propagating an error status from the underlying decode operation. It was logging the error but using the return value from the bplog macro, which will be BP_SUCCESS.
This also updates the coverage tests to use "INT32_EQ" rather than "UINT32_EQ", as the return value from these API calls is a signed integer.
Fixes #252
Testing performed
Unit test cases updated to cover this case
Pass in bundle using unsupported features
Expected behavior changes
The bplib_cla_ingress() function will return BP_ERROR if the bundle being passed in does not decode successfully
System(s) tested on
Debian
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.
Describe the contribution The "bplib_generic_bundle_ingress()" function was not correctly propagating an error status from the underlying decode operation. It was logging the error but using the return value from the bplog macro, which will be BP_SUCCESS.
This also updates the coverage tests to use "INT32_EQ" rather than "UINT32_EQ", as the return value from these API calls is a signed integer.
Fixes #252
Testing performed Unit test cases updated to cover this case Pass in bundle using unsupported features
Expected behavior changes The
bplib_cla_ingress()
function will returnBP_ERROR
if the bundle being passed in does not decode successfullySystem(s) tested on Debian
Contributor Info - All information REQUIRED for consideration of pull request Joseph Hickey, Vantage Systems, Inc.