Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run Vector's tests under valgrind in CI #1499

Closed
ghost opened this issue Jan 9, 2020 · 1 comment
Closed

Run Vector's tests under valgrind in CI #1499

ghost opened this issue Jan 9, 2020 · 1 comment
Labels
domain: tests Anything related to Vector's internal tests

Comments

@ghost
Copy link

ghost commented Jan 9, 2020 •
edited by ghost
Loading

To detect possible memory leaks (mostly in the libraries used over FFI) we can run Vector's tests using valgrind. This should be relatively simple to add, although the tests usually run significantly longer with it.

Because valgrind uses special hooks in GLibc to detect memory leaks, this should be added as a separate job.
@ghost ghost mentioned this issue Jan 9, 2020
Closed
@ghost ghost added domain: operations domain: tests Anything related to Vector's internal tests labels Jan 9, 2020
@ghost
Copy link
Author

ghost commented Jan 28, 2020

This is a duplicate of #825.

@ghost ghost closed this as completed Jan 28, 2020
@lukesteensen lukesteensen mentioned this issue Nov 6, 2020
Merged
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain: tests Anything related to Vector's internal tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants