tests: Symlink volume tests#5284
Conversation
|
Hi @claudiubelu. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Build succeeded.
|
b6b8902 to
2d3b4ca
Compare
|
Build succeeded.
|
2d3b4ca to
92b462b
Compare
|
Build succeeded.
|
92b462b to
6dceda9
Compare
|
Build succeeded.
|
6dceda9 to
f5a3118
Compare
|
Build succeeded.
|
There was a problem hiding this comment.
I haven't looked about to see what the idiom is, but I would have found this clearer to read in the test itself if this was createFileFn, so I was looking for a variable named test, not an imported module named test.
There was a problem hiding this comment.
Sure, will rename test to testCase and createFile to createFileFn. I was doing something similar to this: https://github.com/containerd/containerd/blob/master/integration/pod_hostname_test.go#L36
There was a problem hiding this comment.
Sure, will rename test to testCase and createFile to createFileFn. I was doing something similar to this: https://github.com/containerd/containerd/blob/master/integration/pod_hostname_test.go#L36
|
@claudiubelu: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
f5a3118 to
67ad1c6
Compare
|
Build succeeded.
|
67ad1c6 to
d5addee
Compare
|
Build succeeded.
|
d5addee to
9332bea
Compare
|
Build succeeded.
|
9332bea to
ec14d90
Compare
|
Build succeeded.
|
ec14d90 to
7d0ca13
Compare
|
Build succeeded.
|
7d0ca13 to
2d83dbd
Compare
|
Build succeeded.
|
2d83dbd to
99077b7
Compare
|
Build succeeded.
|
99077b7 to
f49d1b4
Compare
|
Build succeeded.
|
f49d1b4 to
f38cd87
Compare
|
Build succeeded.
|
kzys
left a comment
There was a problem hiding this comment.
@containerd/committers Can someone take a look?
|
Build succeeded.
|
|
Oh! Sorry, I see you used the "suggestions" option on GitHub to include my suggested changes, but unfortunately that adds a commit without a correct DCO sign-off 😞 Could you squash the two commits, and make sure it has your DCO ( |
ac4e56b to
64b9ddb
Compare
|
Build succeeded.
|
There was a known issue regarding how the symlink files mounted as volumes were being handled on Windows. This commit adds tests that will check against those issue to ensure there won't be any regressions. Signed-off-by: Claudiu Belu <[email protected]>
64b9ddb to
93e268f
Compare
|
Build succeeded.
|
There was a known issue regarding how the symlink files mounted as volumes were being handled on Windows. This commit adds tests that will check against those issue to ensure there won't be any regressions.
Related issue: #4915
Signed-off-by: Claudiu Belu [email protected]