476968e2c8
Concurrent access to the same query module had a race condition on the pointer that was used to handle the custom memory management. With this commit, a mapping has been added to keep information about what thread used the pointer to handle the memory resources. This should be fine since the respected query executions are running on a dedicated thread. Access to the mapping itself is threadsafe. A simple RAII wrapper for the mapping container has also been added for simpler client-side use. |
||
|---|---|---|
| .. | ||
| analytical_mode | ||
| analyze_graph | ||
| batched_procedures | ||
| concurrent_query_modules | ||
| configuration | ||
| disk_storage | ||
| fine_grained_access | ||
| graphql | ||
| init_file_flags | ||
| isolation_levels | ||
| lba_procedures | ||
| load_csv | ||
| magic_functions | ||
| memory | ||
| mock_api | ||
| module_file_manager | ||
| monitoring_server | ||
| python_query_modules_reloading | ||
| replication | ||
| server | ||
| streams | ||
| telemetry | ||
| temporal_types | ||
| transaction_queue | ||
| triggers | ||
| write_procedures | ||
| .gitignore | ||
| CMakeLists.txt | ||
| interactive_mg_runner.py | ||
| memgraph-selfsigned.crt | ||
| memgraph-selfsigned.key | ||
| memgraph.py | ||
| mg_utils.py | ||
| pytest_runner.sh | ||
| README.md | ||
| run.sh | ||
| runner.py | ||
tests/e2e
Framework to run end-to-end tests against Memgraph.
Notes
- If you change something under this directory and below (even a Python
script),
makehas to be run again because all tests are copied to the build directory and executed from there. - Use/extend
run.shif you run any e2e tests:- if all tests have to executed, use
run.sh - if a suite of tests have to be execute, take a look under
run.shhow to do so - if only a single test have to be execute, take a look at each individual binary/script, it's possible to manually pick the test
- if all tests have to executed, use