Skip to content
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

integration test not working on Windows #10854

Closed
rustyx opened this issue Jun 26, 2019 · 5 comments
Closed

integration test not working on Windows #10854

rustyx opened this issue Jun 26, 2019 · 5 comments

Comments

@rustyx
Copy link

rustyx commented Jun 26, 2019

The integration package, which is very useful for integration testing, isn't working on Windows:

func TestEtcd(t *testing.T) {
	c := integration.NewClusterV3(t, &integration.ClusterConfig{
		Size: 3,
	})
	defer c.Terminate(t)
}

Throws:

cluster.go:485: listen unix 127.0.0.1:2100111204: bind: The requested address is not valid in its context.

How to instantiate an in-memory cluster on Windows?

@fcddk
Copy link

fcddk commented Jul 16, 2019

I recommend deploying etcd on a Linux virtual machine. It is easy to get an answer when encountering an error.

@xkisu
Copy link

xkisu commented Aug 7, 2019

I am also experiencing this problem

@xkisu
Copy link

xkisu commented Aug 7, 2019

I believe this is related to #6959, more specifically to how addresses are being handled here https://github.com/etcd-io/etcd/blob/master/integration/bridge.go#L46

@stale
Copy link

stale bot commented Apr 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 6, 2020
@rustyx
Copy link
Author

rustyx commented Apr 6, 2020

This is about the integration package which is the recommended way of creating an in-memory temporary cluster. It does not work on Windows. Even though etcd standalone server obviously does.

@stale stale bot removed the stale label Apr 6, 2020
@stale stale bot closed this as completed Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants