Skip to content

Run tests in parallel #174

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

Closed
Gerold103 opened this issue Mar 11, 2019 · 4 comments
Closed

Run tests in parallel #174

Gerold103 opened this issue Mar 11, 2019 · 4 comments
Labels
refactoring Code refactoring
Milestone

Comments

@Gerold103
Copy link
Collaborator

For that it is required to use zero port to bind, and deal with filtering out all the URIs from result files.

@Gerold103 Gerold103 added the refactoring Code refactoring label Mar 11, 2019
@Gerold103 Gerold103 added this to the 0.3 milestone Mar 11, 2019
@Gerold103
Copy link
Collaborator Author

It is not as trivial as I thought - URIs are fixed in config. Possible solution - start tarantools on zero port, collect real ports, fill them into a config, use that config.

@Totktonada
Copy link
Member

use_unix_sockets and use_unix_sockets_iproto options did help me for graphql (if you are about flaky fails). There is also an issue in test-run to fix that: tarantool/test-run#141 (but nobody will do it, I think).

@Gerold103
Copy link
Collaborator Author

@Totktonada - not about flakiness. It is about a necessity to write all the URIs into configuration tables/files before Tarantool start. If do so, 1) parallel tests would collide on the same ports, 2) ports could be occupied already by not Tarantool. Probably unix sockets could help, if they are stored separately for each test in var/ dir. Are they? Then I could hardcode them into configs, and at the same time do not bump into collisions of different tests.

@Gerold103
Copy link
Collaborator Author

This #371 will solve the problem. In the current diff-tests it is not realistic. Will need to rewrite them fully anyway for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code refactoring
Projects
None yet
Development

No branches or pull requests

2 participants