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

parallelize tests/kdb #2024

Open
ingwinlu opened this Issue May 25, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@ingwinlu
Contributor

ingwinlu commented May 25, 2018

The tests in tests/kdb are some of the longest running tests in the repository. They currently have to be run serial as they all modify the key database.

Can we create a tmpdir for each of those tests with a new key database for each of the test suites?
This would shave some time of the more expensive test runs.

@markus2330

This comment has been minimized.

Contributor

markus2330 commented May 25, 2018

Thank you for reporting the problem!

Can we create a tmpdir for each of those tests with a new key database for each of the test suites?

Tests write into the system and spec namespaces, which are paths fixed at compile-time. So it would only be possible:

  1. if we recompile Elektra for every test (or parts of tests).
  2. fix the race tests #137 and the semlock plugin #1399 which would completely serialize all KDB accesses to avoid any conflict. Then parallel access would not matter, except if the very same key is overwritten which should not happen because we use /tests/testname as prefixes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment