-
Notifications
You must be signed in to change notification settings - Fork 28
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
virtionet: testing connectUnixPath #199
Conversation
d52b77c
to
cf719ce
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.
Thanks for adding this test! A few minor comments.
}) | ||
|
||
t.Run("Failed connection - End socket longer than 104 bytes", func(t *testing.T) { | ||
// Retrieve HOME env variable (used by the os.UserHomeDir) |
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.
Ah right, kind of messy to do the 100 bytes test with current main
:/ This will need to be modified once #195 gets in.
Can you squash all 3 commits together? I don't think it's really useful to keep all 3 in our git history. |
ed32f4f
to
e77812d
Compare
@cfergeau updated |
it adds tests for connectUnixPath and localUnixSocketPath func in virtionet.go it mainly test the use case where one end of the unixgram socket is longer of 104 bytes resulting in a failure. On macOS, a path on the filesystem can have a max of 104 bytes length
e77812d
to
d7b2799
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfergeau The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
It adds tests for connectUnixPath and localUnixSocketPath func in virtionet.go.
It mainly test the use case where one end of the unixgram socket is longer of 104 bytes resulting in a failure.