memgraph/tests
florijan e26456d5ad Fix durability test flakyness
Summary:
It occurred that part of the durability flakyness test might be that the
same durability directory is used always. If the test is run
simultaneously on a single system, there will be interference.

This might not actually fix all the flakyness :(

I also made the `utils::RandomString` function since that's now used in
multiple places, tested it etc.

Reviewers: buda, dgleich

Reviewed By: dgleich

Subscribers: pullbot

Differential Revision: https://phabricator.memgraph.io/D1020
2017-12-04 13:46:56 +01:00
..
benchmark Prepare transactional engine for distributed 2017-12-01 09:17:44 +01:00
concurrent Prepare transactional engine for distributed 2017-12-01 09:17:44 +01:00
data Replace map with bitset in stripped query 2017-08-02 22:17:36 +02:00
drivers Add C# driver test examples 2017-11-10 15:46:56 +01:00
macro_benchmark Remove extension from Python executables 2017-11-27 14:39:51 +01:00
manual Migrate labels/properties/edgetypes to ids 2017-11-23 17:12:37 +01:00
property_based Migrate labels/properties/edgetypes to ids 2017-11-23 17:12:37 +01:00
public_benchmark Remove extension from Python executables 2017-11-27 14:39:51 +01:00
qa Add nodes and relationships functions 2017-10-30 12:38:12 +01:00
stress Remove extension from Python executables 2017-11-27 14:39:51 +01:00
unit Fix durability test flakyness 2017-12-04 13:46:56 +01:00
client-stress.sh Migrate command line args to gflgs in tests 2017-07-06 13:54:12 +02:00
CMakeLists.txt Remove unused stuff from CMakeLists 2017-10-16 13:45:18 +02:00