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@(a)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 <lslebodn(a)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
---
Can we get it merged? If not, then why?
Thank you.
LS