[CLIENT-2239] CI/CD: Use massif to get Python client memory usage over time while running integration tests #664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed pytest-memray test, since it's not needed for CI/CD regression testing; only for debugging
Note: Did not test the last commit: Show massif output even if tests failed
Testing:
Metrics code has a memory leak. Massif does show increased memory usage (double that of
dev
): https://github.com/aerospike/aerospike-client-python/actions/runs/10706083490/job/29682962437#step:12:19Run on
dev
: https://github.com/aerospike/aerospike-client-python/actions/runs/10690461665/job/29634968764#step:13:20Can still run
memcheck
. No regression in ci/cd code: https://github.com/aerospike/aerospike-client-python/actions/runs/10690463167/job/29634968672