-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(agw): fix always-true-asserts in s1ap integ tests #14091
Conversation
Thanks for opening a PR! 💯
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
Oops! Looks like you failed the Howto
♻️ Updated: ✅ The check is passing the Python Format Check after the last commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grepping for assert (
gives one more assert
statements with parentheses and a comma inside to double check, please:
test_agw_offload_mixed_idle_active_multiue.py
BTW, there is a proposal to adapt the currently wrong syntax as allowed, LINK.
And check the python linter, please.
2c0ada6
to
431a0a3
Compare
Signed-off-by: Sebastian Wolf <sebastian.wolf@tngtech.com>
431a0a3
to
2d4f89a
Compare
Signed-off-by: Sebastian Wolf <sebastian.wolf@tngtech.com> Signed-off-by: Sebastian Wolf <sebastian.wolf@tngtech.com>
Signed-off-by: Sebastian Wolf sebastian.wolf@tngtech.com
Summary
After #14012 , some asserts were using an incorrect syntax that always yields true:
assert(condition, "description")
. This PR changes these to function as intended:assert condition, "description"
Example warning:
Affected tests:
test_agw_offload_idle_active_ue
test_attach_detach_multiple_rar_tcp_data
test_attach_detach_rar_tcp_data
test_attach_detach_rar_tcp_he
test_attach_detach_setsessionrules_tcp_data
test_attach_detach_with_ovs
Test Plan
Run the affected tests and see that the warnings disappear.
Additional Information