-
Notifications
You must be signed in to change notification settings - Fork 90
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.
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
lib389 - valgrind functions need improvement #1604
Comments
Comment from mreynolds (@mreynolds389) at 2015-09-16 04:23:03 lib389 valgrind function improvement |
Comment from nhosoi (@nhosoi) at 2015-09-16 07:15:57 git patch file (master) -- CI test for 48226 - additional check for a memory leak. |
Comment from nhosoi (@nhosoi) at 2015-09-16 07:17:46 Hi Mark, thanks for the valgrind enhancement. Could you please add the diff to the patch? Actually, it revealed another leak in 48226... I'm reopening the ticket... |
Comment from mreynolds (@mreynolds389) at 2015-09-16 09:13:09 revision with Noriko's diffs |
Comment from mreynolds (@mreynolds389) at 2015-09-16 09:14:35 Replying to [comment:2 nhosoi]:
New patch attached with your revisions. Thanks, |
Comment from nhosoi (@nhosoi) at 2015-09-16 23:01:30 Thank you, Mark! Ack'ed. |
Comment from mreynolds (@mreynolds389) at 2015-09-17 00:02:15 Lib389 To ssh://git.fedorahosted.org/git/389/lib389.git 389-ds-base To ssh://git.fedorahosted.org/git/389/ds.git 5f32582..5165d58 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 16bd6af..c7ac0ad 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 |
Comment from mreynolds (@mreynolds389) at 2017-02-11 22:58:05 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48273
Currently the valgrind function valgrind_check_leak() looks at the process output(ps -ef), then stops the server, and looks at the output. This means that you can only can this function once, all future checks will fail since the process was stopped. Check leaks should not stop the server or check the the process output for the valgrind output file. The output file should be gathered after valgrind is enabled, and before we check for leaks, so it can be checked multiple times. The server should also not be stopped when checking for leaks.
The wiki page for lib389 valgrind testing will need to be amended once a fix is done.
The text was updated successfully, but these errors were encountered: