Matija Santl d387bac544 Fail HA benchmark on non-zero exit status ... Summary: For HA benchmarks, if one of the executables exits with a status other than zero, the benchmark should fail. Also, removing `LOG(INFO)`, since failing benchmarks should flag where to look. Reviewers: ipaljak Reviewed By: ipaljak Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D1921		2019-03-14 16:53:58 +01:00
..
benchmark	Add micro benchmark for existence constraint	2019-02-21 08:56:12 +01:00
concurrent	Remove unused variables	2019-01-15 15:30:34 +01:00
distributed	Improve card fraud test startup	2019-03-06 13:38:48 +01:00
drivers	Integrate driver tests with Apollo	2018-08-22 18:31:37 +02:00
feature_benchmark	Fail HA benchmark on non-zero exit status	2019-03-14 16:53:58 +01:00
integration	Implement LDAP authentication	2019-02-28 09:39:30 +01:00
macro_benchmark	Build mg-comm-rpc library	2019-02-07 14:40:15 +01:00
manual	Add wal for ExistenceConstraints	2019-03-06 08:52:00 +01:00
property_based	Remove virtual and pimpl from single node	2018-10-09 11:48:30 +02:00
public_benchmark	Update LDBC query implementation	2018-07-10 10:08:21 +02:00
qa	Refactor QA	2018-12-04 12:33:48 +01:00
stress	Polish Bolt client and mg_client	2018-10-19 13:55:51 +02:00
unit	Switch from Cache to LruCache	2019-03-12 16:11:03 +01:00
apollo_runs.py	Add LCP tests	2018-10-15 11:52:20 +02:00
client-stress.sh	Migrate command line args to gflgs in tests	2017-07-06 13:54:12 +02:00
CMakeLists.txt	Add kafka benchmark	2018-08-29 16:35:31 +02:00