From dfdbb358177fd664bdde0630ef50c91e184baf13 Mon Sep 17 00:00:00 2001 From: drebs Date: Tue, 18 Apr 2017 10:47:44 +0200 Subject: [test] avoid running sqlcipher synchonous tests when benchmarking SQLCipher synchronous benchmark tests were introduced when we started developing benchmark tests to compare synchronous and asynchronous code. Synchronous access to sqlcipher database is not used in soledad, and those tests are much slower than asynchronous tests (more than 10 times using ssd drive), so we want to avoid running them on ci. This commit introduces a "synchronous" marker and avoid running tests markes as such in ci environment. --- testing/tests/benchmarks/test_sqlcipher.py | 1 + 1 file changed, 1 insertion(+) (limited to 'testing/tests') diff --git a/testing/tests/benchmarks/test_sqlcipher.py b/testing/tests/benchmarks/test_sqlcipher.py index 39c9e3ad..0cdda7e6 100644 --- a/testing/tests/benchmarks/test_sqlcipher.py +++ b/testing/tests/benchmarks/test_sqlcipher.py @@ -22,6 +22,7 @@ def build_test_sqlcipher_async_create(amount, size): def build_test_sqlcipher_create(amount, size): + @pytest.mark.synchronous @pytest.mark.benchmark(group="test_sqlcipher_create") def test(soledad_client, benchmark, payload): client = soledad_client()._dbsyncer -- cgit v1.2.3