Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 8978
  • 8938
  • benchmark-all-commits
  • debian_package
  • onepython
  • benchmark_elasticsearch
  • buildpackage
  • debian/platform-0.9
  • release/0.9.x
  • feature/streaming-transfer
  • debian/experimental-0.9
  • debian/experimental
  • debian/platform-0.8
  • bug/remove-unicode-conversion
  • release/0.8.x
  • release/0.7.x
  • release/bitmask-0.9.x-alpha
  • debian/platform-0.7
  • release/0.6.x
  • 0.10.5
  • 0.10.4
  • 0.9.6post3
  • 0.10.3
  • 0.10.2
  • 0.10.1
  • 0.10.0
  • 0.9.3post3
  • 0.9.6post2
  • 0.9.6post1
  • 0.9.6
  • 0.9.5
  • 0.9.3
  • 0.9.2
  • 0.9.1
  • 0.9.0
  • 0.9.0rc1
  • 0.8.1
  • 0.8.0
  • 0.7.4
40 results

test_sqlcipher.py

  • drebs's avatar
    e8ae4d59
    [benchmarks] limit number of runs of sqlcipher benchmark tests · e8ae4d59
    drebs authored 
    As sqlcipher benchmark tests take longer, we want to limit the number of
repetitions. Previous to this change, these tests were being calibrated
automatically and would run 5 times becuase it is the default minimum
number of times for pytest-benchmark. By changing the runner to pedantic
mode, now they will be run 4 times, the same number of times as
benchmark sync tests.
    Verified
    e8ae4d59
    History
    [benchmarks] limit number of runs of sqlcipher benchmark tests
    drebs authored 
    As sqlcipher benchmark tests take longer, we want to limit the number of
repetitions. Previous to this change, these tests were being calibrated
automatically and would run 5 times becuase it is the default minimum
number of times for pytest-benchmark. By changing the runner to pedantic
mode, now they will be run 4 times, the same number of times as
benchmark sync tests.