memgraph

tursom/memgraph

Fork 0

Files

History

Marko Budiselic 6fe9da2578 gbenchmark reports are generated inside build/test_results/benchmark

2016-12-23 09:58:26 +01:00

basic_bloom_filter.cpp

unit test normalization

2016-12-22 19:22:45 +01:00

block_allocator.cpp

Bugs from concurrent tests aren't solved. TODO: we have to introduce memory tracker for tests

2016-12-21 21:33:58 +01:00

chunked_decoder.cpp

unit test normalization

2016-12-22 19:22:45 +01:00

chunked_encoder.cpp

unit test normalization

2016-12-22 19:22:45 +01:00

CMakeLists.txt

gbenchmark reports are generated inside build/test_results/benchmark

2016-12-23 09:58:26 +01:00

concurrent_list.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

concurrent_map.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

concurrent_set.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

cypher_state_machine.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

dynamic_bitset.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

parameter_index.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

program_argument.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

ptr_int.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

README.md

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

rh_hashmap.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

rh_hashmultimap.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

signal_handler.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

skiplistset.cpp

Fixed tests.

2016-08-19 19:09:24 +01:00

stack_allocator.cpp

Bugs from concurrent tests aren't solved. TODO: we have to introduce memory tracker for tests

2016-12-21 21:33:58 +01:00

template_engine.cpp

mistake, I forgot to add some changes

2016-12-22 19:28:21 +01:00

README.md

All unit test should be gtest because in that case the test infrastructure can then visualize the results. (JUnit xml output)