On 09/15/2014 10:57 PM, Lukas Slebodnik wrote:
On (02/09/14 15:38), Lukas Slebodnik wrote:
On (02/09/14 14:23), Nikolai Kondrashov wrote:
On 09/02/2014 02:13 PM, Lukas Slebodnik wrote:
On (02/09/14 13:27), Nikolai Kondrashov wrote:
On 09/02/2014 01:02 PM, Lukas Slebodnik wrote:
We use talloc and valgrind needn't find memory leaks.
For this purpose, we have functions in file src/tests/leak_check.c
BTW
For tesing purposes, I reverted commit d528e4960bf233bc002f9676919ede196c91564c
Ah, this one is a good source of a failure.
Thanks Lukas, this seems to work fine with the exception of this one error
in refcount-tests:
==2842== Syscall param timer_create(evp) points to uninitialised byte(s)
==2842== at 0x977FE72: timer_create@@GLIBC_2.3.3 (timer_create.c:82)
==2842== by 0x4E3647B: srunner_run (in /usr/lib64/libcheck.so.0.0.0)
==2842== by 0x401616: main (refcount-tests.c:233)
==2842== Address 0xffefff460 is on thread 1's stack
Patch for this issue is on the list:
"[PATCH] refcount-tests: Do not force to run test in CK_FORK mode"
I updated also readme file and new version is attached.
This patch is blocked by ""[PATCH] refcount-tests: ..."
LS
From 4b20f833f71c9014b0874b5a899d71f0bdbf9ca3 Mon Sep 17 00:00:00 2001
From: Lukas Slebodnik <lsleb...@redhat.com>
Date: Tue, 2 Sep 2014 12:00:03 +0200
Subject: [PATCH] CI: Do not try to find memory leaks with valgrind
We use talloc and valgrind needn't find memory leaks.
For this purpose, we have functions in file src/tests/leak_check.c
---
!!!bump!!!
Two weeks are left and we still don't have all patches on the list
for suppressing memory leaks reported by valgrind.
It's very bad that we ignoring result of failed valgrind test,
it will be better to push patch from previous mail.
I wouldn't say it's "very bad", it is actually better than it was without CI
at all, but it will be more useful to simply have memory leaks ignored and
enforce the rest of the tests, than none.
Unfortunately, I don't have time right now to re-test this nor to continue
working on suppressing leaks, as I have to work on a FreeRADIUS release.
The good news is I managed to suppress/fix all the leaks except of a few
appearing on RHEL6. I'll resume the work once I deal with FreeRADIUS.
Meanwhile, could someone please review the test leak fixes I posted earlier?
Thank you.
Nick
_______________________________________________
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
