test: remove K8sDatapathBandwidthTest#44226
Conversation
2786d84 to
07db665
Compare
|
Where is this functionality being tested if it's not tested in the |
|
it's in cilium/cilium-cli/connectivity/builder/network_bandwidth_limit.go Lines 13 to 17 in 74c333d |
|
I see, thanks for pointing that out. Can you describe how you made sure that these changes won't reduce coverage over the feature? |
|
The Ginkgo bandwidth test was already not running in CI. It only ran on net-next kernels, but the focus group that included it was excluded from the net-next job exclude:
# The bandwidth test is disabled and hubble tests are not meant
# to run on net-next.
- k8s-version: "1.35"
focus: "f10-agent-hubble-bandwidth"basically it never ran anywhere, so what I did was just removed the dead code |
pchaigno
left a comment
There was a problem hiding this comment.
Could you repeat in the commit description the additional context you gave in response to Joe's question? Other than that, looks good to me.
The Ginkgo bandwidth test was already not running in CI. It only ran on net-next kernels, but the focus group that included it (f10-agent-hubble-bandwidth) was excluded from the net-next job. Bandwidth enforcement is independently tested in cilium-cli/connectivity/builder/network_bandwidth_limit.go. Fixes: cilium#44165 Related: cilium#37837 Signed-off-by: Pavan More <pavansmore05@gmail.com>
07db665 to
d810de5
Compare
pchaigno
left a comment
There was a problem hiding this comment.
Thanks for the contribution!
|
/test |
Changes:
test/k8s/bandwidth.go.github/actions/ginkgo/main-focus.yamltest/ginkgo-ext/junit_reporter.goCODEOWNERSFixes: #44165
Related: #37837