soledad.git - [soledad]

Age	Commit message (Collapse)	Author
2017-09-17	[refactor] move tests to root of repository	drebs
	Tests entrypoint was in a testing/ subfolder in the root of the repository. This was made mainly because we had some common files for tests and we didn't want to ship them (files in testing/test_soledad, which is itself a python package. This sometimes causes errors when loading tests (it seems setuptools is confused with having one python package in a subdirectory of another). This commit moves the tests entrypoint to the root of the repository. Closes: #8952
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-07-18	[benchmarks] add docstrings for benchmarks	drebs

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

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-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-04	[feat] add the host hostname to benchmark machine info	drebs

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

2016-12-12	[test] rename benchmark tests directory and tag	drebs