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
test: Remove Services SCTP test case #16895
Conversation
0d61fa0
to
367c22d
Compare
test-1.16-netnext |
net-next hit #12511. Considering that the test removal doesn't have anything to do with it, no need to re-run tests. |
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.
LGTM apart from a comment about iperf3-deployment.yaml
.
367c22d
to
d8a6ce8
Compare
The test case is supposed to test whether the BPF NAT engine doesn't drop packets of a type which it doesn't support (e.g. SCTP). However, recently the test case became flaky. Considering this and a little value the test provides, let's remove the test case. Instead, we should create a BPF unit test for it once it's available (#16862). Signed-off-by: Martynas Pumputis <m@lambda.lt>
Considering that the new change after the net-next had passed is the removal of the manifest file (not used by any of the tests), marking it as ready to merge. |
The test case is supposed to test whether the BPF NAT engine doesn't
drop packets of a type which it doesn't support (e.g. SCTP). However,
recently the test case became flaky. Considering this and a little value
the test provides, let's remove the test case.
Instead, we should create a BPF unit test for it once it's available
(#16862).
I've reopened #10541 and updated the description.
Fix #16838
Fix #16839