-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add integration test for linux and update go version from 1.16 to 1.17 #84
Conversation
df835e6
to
92c1186
Compare
Codecov Report
@@ Coverage Diff @@
## main #84 +/- ##
=======================================
Coverage 44.41% 44.41%
=======================================
Files 9 9
Lines 403 403
=======================================
Hits 179 179
Misses 190 190
Partials 34 34 Continue to review full report at Codecov.
|
b6bd06d
to
0eec5a2
Compare
integration_linux_test.go
Outdated
// | ||
// NOTE: | ||
// | ||
// 1. It required that the both bridge and loopback CNI plugins are installed |
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.
t.Skip when the requirement is not satisfied
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.
Currently, we only have mockCNI
case in this repo. And the new case is based on real plugin, which can help us to detect potential issue, like data-race. I think it should fail if the requirement is not satisfied.
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.
It should still be skippable. Just skipping based on a missing requirement isn't the best approach since an error in setup could just end up causing a skip. I might suggest either skipping on testing.Short
or putting the integration test in a sub-package
37e0682
to
911066e
Compare
@dmcgowan @AkihiroSuda Updated. PTAL. Thanks! |
6334447
to
41d9753
Compare
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 .. two nits to consider
- maybe remove coverage as was done for other projects?
- split the go-cni and go-cni/integration tests into two separate tests? in case these particular plugins are not avail for certain platforms going forward.. for example windows (or we could split later I suppose and refactor when we add here)
Thanks Mike. I can remove coverage. But I don't quite understand the second part nit 😂 I will discuss with you when you are back. :) |
* Use real CNI plugins to test Setup/Remove API. * Update go version from 1.16.x to 1.17.x in CI. * Remove coverage Signed-off-by: Wei Fu <[email protected]>
Paste the result:
|
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
Signed-off-by: Wei Fu [email protected]