Hi, On Mon, Dec 2, 2024 at 5:06 AM Michael Prokop <m...@debian.org> wrote: > So it sadly still doesn't seem to work on amd64. :( > Quoting from > https://ci.debian.net/packages/s/sssd/testing/amd64/54970410/: > > | test ldap-user-group-ldap-auth: test run > | [...] > | 86s + [ testuser1 ldapusers != testuser1 ldapusers ] > | 86s + echo The LDAP user can login on a terminal > | 86s + /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1secret > | 86s spawn login > | 86s send: spawn id exp3 not open > | 86s while executing > | 86s "send "$user\r"" > | 86s (file "debian/tests/login.exp" line 21) > | 86s autopkgtest [19:20:51]: test ldap-user-group-ldap-auth: > -----------------------] > | ▾ test ldap-user-group-ldap-auth: test results > | 86s autopkgtest [19:20:51]: test ldap-user-group-ldap-auth: - - - - - - - > - - - results - - - - - - - - - - > | 86s ldap-user-group-ldap-auth FAIL non-zero exit status 1 > > It doesn't seem to be about the timeout now. :-/ > Looks like our only option for now seems to be disabling this > specific autopkgtest until someone found a way how to reproduce it?
We could, in no particular order: a) Move this test into its own test file, and mark that one as flaky. Then at least we don't lose the coverage of the other checks in this test, but the setup bit is definitely a duplication b) Check if running on debian, then if it fails, ignore the failure but log a lot of extra stuff to help (yuck for the "if on debian" part) c) Maybe (a) and (b), so that it is still gating on ubuntu, where mysteriously it works d) mark the whole test as flaky, as suggested, but add a ton of logging when it fails. I might remove the flaky tag as an ubuntu delta, though (we have some trivial delta already). e) ignore failure in that last expect test only (perhaps only when on debian, since it mysteriously always works in ubuntu?) , and grab a ton of logging. Keep the test marked as non-flaky.
