Use different containerd sock address for integration test client#9415
Use different containerd sock address for integration test client#9415mikebrow merged 1 commit intocontainerd:mainfrom
Conversation
|
The address is configurable via the flag, can't we just pass the flag when we run our tests? (or locally when a user is running the tests they can provide the flag) |
Hmm isn't the -address flag for the tests mostly to know which sock address to connect to? It would be nice to have parity in how the test daemon is started when the '--no-daemon' flag is not specified. That is start on a different non-default sock address for the tests. like npipe:\containerd-containerd-test |
Also, tests like the following try to get the ttrpc address from the "address" set in TestMain() which is a unique test only sock address in 1.6 which makes more sense: |
|
If the test address is now same as the default address for the platform and if this is already open, tests would fail while trying to open same pipe |
40054df to
18a48d8
Compare
It may be (I'm reviewing on mobile so didn't do great due diligence 😅). The description made it seem like thats the addr it'd listen on if they were launching the daemon |
|
/retest |
18a48d8 to
c21bc30
Compare
e4212a6 to
5f1e9a6
Compare
5f1e9a6 to
c51ce11
Compare
c51ce11 to
fe9f2b5
Compare
7fb6e0a to
6c4ad26
Compare
6c4ad26 to
00a703e
Compare
|
@fuweid @cpuguy83 @mikebrow @MikeZappa87 could you please take a look when you have some time please? Thanks! |
|
@fuweid @cpuguy83 @mikebrow @MikeZappa87 could you please take a look at this PR? |
00a703e to
fd81b19
Compare
|
/retest |
fd81b19 to
e7b8a18
Compare
Signed-off-by: Kirtana Ashok <[email protected]>
e7b8a18 to
5b6ae0f
Compare
If the containerd/containerd/defaults.DefaultAddress is used , it causes failures if containerd is already running on the default address and the tests are run without the 'no-daemon' flag.
It would be good to use a different containerd sock address for integration tests