Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(unit-tests): stop triggering health checks in longevity unit test
The 'test_longevity.py::test_test_user_batch_custom_time' unit test uses the 'test-cases/scale/longevity-5000-tables.yaml' config file for running a short longevity test which triggers a nemesis. If health checks are enabled then the "nemesis call" runs much longer while health checks are completed 2 times - before and after the nemesis. And while it is ongoing the nemesis lock gets held. And the problem with it is that it runs even after finish of this test. So, any another unit test which tries to get a nemesis lock will stumble upon a held lock for 10+ minutes. It started happening after the merge of the PR [1] which enabled health checks in the mentioned config file. The affected test is following: - test_nemesis.py::test_list_nemesis_of_added_disrupt_methods Alphabetically it runs after the 'test_longevity.py::test_test_user_batch_custom_time' one. So, disable health checks to avoid side-effects and doing redundant stuff which were not planned when the test was written. [1] scylladb#9843 (cherry picked from commit a78d65f)
- Loading branch information