soledad.git - [soledad]

Age	Commit message (Collapse)	Author
2017-09-11	[test] selectivelly start events server on benchmarks	drebs
	Soledad's events server might be a pain for tests because if it is not properly initialized and shut down there might be parts of the server missing or leftover in the reactor after tests are run. With the recent changes to the way tests are invocated, there's the need to further isolate events server startup for benchmarks, otherwise it will conflict with other tests. This commit moves the events server setup to inside the pytest_collection_modifyitems() hook, where we can check if the benchmark subdir was selected and properly start the events server if needed.
2017-09-11	[benchmarks] add responsiveness test with watchdog	drebs

2017-09-08	[test] allow test_vs_legacy test to run with remote server	drebs

2017-09-05	[test] refactor and fixes for blobs vs legacy test	drebs
	- create payloads before running tests - use different group names for different amount/sizes - move legacy index creation to setup function - limit concurrency on blobmanager to 2 (same as thread pool size) - add a VACUUM call to observe blobs db size decreasing between tests - properly cleanup server between blobs test runs - refactor blobs pipeline so it makes more sense and is easier to read
2017-08-31	[test] use semaphore in legacy vs blobs test	drebs

2017-08-25	[benchmarks] add legacy mail delivery test	drebs

2017-07-18	[benchmarks] add docstrings for benchmarks	drebs

2017-07-18	[benchmarks] store test function docstring	drebs

2017-07-13	[doc] add info on how to update benchmarks website	drebs

2017-07-13	[benchmarks] change 20_500k to 10_1000k	drebs

2017-07-12	[doc] mark which sync benchmark scenarios are actually run	drebs

2017-07-12	[benchmarks] limit number of runs of sqlcipher benchmark tests	drebs
	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.
2017-07-12	[benchmarks] allow passing args and kwargs to txbenchmark_with_setup	drebs

2017-07-09	[benchmarks] separate memory sampling from cpu measurement	drebs

2017-07-08	[benchmarks] run benchmarks twice, for time and resources	drebs
	We noticed that instrumentation added for watching resources has an impact in time statistics (i.e. it increases average and stddev). This commit makes the benchmark tests run twice: once for measuring time and a second time for measuring resources.
2017-07-08	[benchmarks] add --watch-resources option	drebs
	This commit adds the --watch-resources command line option for benchmarks tests, and allows to running the benchmark test suite with and without resource monitoring instrumentation code. This is needed because resource consumption monitoring impacts the mean time and standard deviation of time taken to run benchmarked tests.
2017-07-08	[benchmarks] skip some tests by default	drebs

2017-07-07	[test] change memory sampling interval to 0.1 on benchmarks	drebs

2017-04-27	[test] monitor cpu/mem for all benchmarks	drebs

2017-04-27	[test] add memory measurement	drebs

2017-04-27	[test] measure cpu percentage during benchmark	drebs

2017-04-19	[test] avoid running sqlcipher synchonous tests when benchmarking	drebs
	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.
2017-04-04	[feat] add the host hostname to benchmark machine info	drebs

2017-03-02	[test] add comments explaining behaviour of upload/download benchmark	drebs

2017-03-02	[test] mark benchmark tests using their group names	drebs

2017-03-02	[test] bugfix: actually use an empty local db in download benchmarks	drebs
	We were previously not using an empty local db for download benchmark tests, so there was actually nothing to sync. This commit fixes that by adding a way to force an empty local db on soledad client instantiation.
2016-12-12	[feature] Add retro compat on secrets.py ciphers	Victor Shyba
	Integrated the secrets's JSON key that specifies ciphers into _crypto and added optional GCM. Also added a test to check if both cipher types can be imported. Resolves: #8680 Signed-off-by: Victor Shyba <victor1984@riseup.net>
2016-12-12	[feature] use GCM instead of CTR+HMAC	Victor Shyba
	Resolves: #8668 - client: substitute usage of CTR mode + HMAC by GCM cipher mode Signed-off-by: Victor Shyba <victor1984@riseup.net>
2016-12-12	[feature] speed up sync benchmark setup code	Victor Shyba
	We aren't testing huge payloads on CI, so it doesn't make sense to insert docs one by one. 'gatherResults' can speed up bench setup.
2016-12-12	[feature] make _crypto stream on decryption	Victor Shyba
	We are already doing this on encryption, now we can stream also from decryption. This unblocks the reactor and will be valuable for blobs-io.
2016-12-12	[tests] fixes test_crypto bench	Victor Shyba
	encrypt returns a deferred and needs the adapted benchmark runner.
2016-12-12	[tests] use options instead of marks	Victor Shyba
	When we use marks the new pytests from benchmarks folder are collected and ignored, but this causes trial to fail sometimes. Using --ignore avoids it from being loaded while --benchmark-only will properly select the benchmarks for tox, as intended.
2016-12-12	[test] rename benchmark tests directory and tag	drebs