It passed[1] in salsa:
+ /usr/bin/expect -f debian/tests/login.exp testuser1 testuser1secret
The LDAP user can login on a terminal
spawn login
ldap login: testuser1
Password:
Linux ldap.example.com 5.10.0-33-cloud-amd64 #1 SMP Debian 5.10.226-1
(2024-10-03) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Creating directory '/home/testuser1'.
***@ldap:~$ id -un
testuser1
***@ldap:~$ + cleanup
+ result=0
+ set +e
+ [ 0 -ne 0 ]
+ echo ## All tests passed, phew
## All tests passed, phew
autopkgtest [18:02:28]: test ldap-user-group-ldap-auth: -----------------------]
Perhaps we could remove the "set -x"? I wonder if it could interfere sometimes.
1. https://salsa.debian.org/ahasenack/sssd/-/jobs/6539986/viewer#L801
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?
105s + /usr/bin/expect -f debian/tests/login.exp testuser1
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)
-----------------------]
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.
Hi,
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-