I wrote that test initially, and it has been passing in Ubuntu. Sounds like it's some difference in the infrastructure.
I tried locally in a debian LXD container, and it passed just fine. Is it also failing in salsa pipeline runners, or just in the migration by britney? The error seems to indicate that "login" died, or wasn't ready: 105s + /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1kerberos testus...@example.com 105s spawn login 105s send: spawn id exp3 not open 105s while executing 105s "send "$user\r"" 105s (file "debian/tests/login.exp" line 21) 105s autopkgtest [18:34:46]: test ldap-user-group-krb5-auth: -----------------------] These timestamps don't seem to indicate when it happened, but when the log dump happened, right? Otherwise it all happened at 105s basically. If this failure also happens in salsa, then we can inject some debugging into the test in the case of failures. I don't know if I have permissions to trigger a pipeline run in salsa, I'll try with an MP. On Tue, Nov 5, 2024 at 3:57 AM Michael Prokop <m...@debian.org> wrote: > > Hi, > > * Paul Gevers [Sat Sep 07, 2024 at 07:13:21AM +0200]: > > > I looked at the results of the autopkgtest of your package. I noticed that > > it regularly fails. > > > > Because the unstable-to-testing migration software now blocks on > > regressions in testing, flaky tests, i.e. tests that flip between > > passing and failing without changes to the list of installed packages, > > are causing people unrelated to your package to spend time on these > > tests. > > > > Don't hesitate to reach out if you need help and some more information > > from our infrastructure. > > > > Paul > > > > https://ci.debian.net/packages/s/sssd/testing/amd64/51295873/ > > > > 41s The LDAP user can login on a terminal > > 41s + /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1secret > > 41s spawn login > > 41s send: spawn id exp3 not open > > 41s while executing > > 41s "send "$user\r"" > > 41s (file "debian/tests/login.exp" line 21) > > I'm aware of folks looking into that, but AFAICT so far nobody was > able to proberly reproduce the issue - so it feels like really being > a flaky test? Should the ldap-user-group-ldap-auth test get marked > as flaky for now, until someone managed to properly take care of > this? > > IMO sssd needs to make its way into trixie. > > regards > -mika-
