Hi,
I was looking into the remaining downstream test failures and found this bug caused by the FQDN patchset..
On (08/07/16 13:55), Jakub Hrozek wrote:
Hi,
I was looking into the remaining downstream test failures and found this bug caused by the FQDN patchset..
Would it be complicated to write an integration test?
LS
On Fri, Jul 08, 2016 at 02:03:16PM +0200, Lukas Slebodnik wrote:
On (08/07/16 13:55), Jakub Hrozek wrote:
Hi,
I was looking into the remaining downstream test failures and found this bug caused by the FQDN patchset..
Would it be complicated to write an integration test?
I guess not, let me try.
On (08/07/16 14:10), Jakub Hrozek wrote:
On Fri, Jul 08, 2016 at 02:03:16PM +0200, Lukas Slebodnik wrote:
On (08/07/16 13:55), Jakub Hrozek wrote:
Hi,
I was looking into the remaining downstream test failures and found this bug caused by the FQDN patchset..
Would it be complicated to write an integration test?
I guess not, let me try.
I tried to write a integration test for this bug but in both cases sssd-client got nss error code NOTFOUND.
But error messages from sssd_nss.log and sssd_domain_log are gone.
ACK
LS
On (01/08/16 11:44), Lukas Slebodnik wrote:
On (08/07/16 14:10), Jakub Hrozek wrote:
On Fri, Jul 08, 2016 at 02:03:16PM +0200, Lukas Slebodnik wrote:
On (08/07/16 13:55), Jakub Hrozek wrote:
Hi,
I was looking into the remaining downstream test failures and found this bug caused by the FQDN patchset..
Would it be complicated to write an integration test?
I guess not, let me try.
I tried to write a integration test for this bug but in both cases sssd-client got nss error code NOTFOUND.
But error messages from sssd_nss.log and sssd_domain_log are gone.
ACK
http://sssd-ci.duckdns.org/logs/job/50/63/summary.html
master: * 64175969779e51c00a78397746d4fec7ce7033a4
LS
sssd-devel@lists.fedorahosted.org
-
Jakub Hrozek -
Lukas Slebodnik