Re: [SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-31 Thread Jakub Hrozek
On Fri, Aug 28, 2015 at 03:19:42PM +0200, Petr Cech wrote: > On 08/27/2015 05:49 PM, Michal Židek wrote: > > > >I agree. Attached is the same patch that was already ACKed, > >just with the changed name and added const. > > > >Michal > > Yes, it is the same, with const. > > ACK again. > > Petr

Re: [SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-28 Thread Petr Cech
On 08/27/2015 05:49 PM, Michal Židek wrote: I agree. Attached is the same patch that was already ACKed, just with the changed name and added const. Michal Yes, it is the same, with const. ACK again. Petr ___ sssd-devel mailing list

Re: [SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-27 Thread Michal Židek
On 08/27/2015 01:01 PM, Lukas Slebodnik wrote: On (19/08/15 20:26), Michal Židek wrote: Hi! This is another patch to avoid failing tests in the CI (make-check-valgrind). This time the ldap_id_cleanup tests. Looks like the one second cache timeout was too short and the tests sometimes failed

Re: [SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-27 Thread Lukas Slebodnik
On (19/08/15 20:26), Michal Židek wrote: Hi! This is another patch to avoid failing tests in the CI (make-check-valgrind). This time the ldap_id_cleanup tests. Looks like the one second cache timeout was too short and the tests sometimes failed because they expected the entries to be still valid

Re: [SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-20 Thread Petr Cech
On 08/19/2015 08:26 PM, Michal Židek wrote: Hi! This is another patch to avoid failing tests in the CI (make-check-valgrind). This time the ldap_id_cleanup tests. Looks like the one second cache timeout was too short and the tests sometimes failed because they expected the entries to be still

[SSSD] [PATCH] TESTS: ldap_id_cleanup timeouts

2015-08-19 Thread Michal Židek
Hi! This is another patch to avoid failing tests in the CI (make-check-valgrind). This time the ldap_id_cleanup tests. Looks like the one second cache timeout was too short and the tests sometimes failed because they expected the entries to be still valid for a short while after they were added