Flaky DEP8 test: saslauthd

[Andreas Hasenack]

It looks like the saslauthd test is a bit flaky, and more so in platforms like arm64[1]:

autopkgtest [15:14:52]: test saslauthd: [-----------------------
Setting up saslauthd with mecanism sasldb
Authentication of user user1887 with correct password should succeed... FAIL
exit status: 255
output:
connect() : No such file or directory
0:
autopkgtest [15:14:53]: test saslauthd: -----------------------]
autopkgtest [15:14:53]: test saslauthd: - - - - - - - - - - results - - - - - - - - - -
saslauthd FAIL non-zero exit status 1

The "connect()" error looks like the saslauthd unix socket isn't ready yet. That test happens right after a saslauthd restart:

    echo "Setting up saslauthd with mecanism ${mech}"
    setup_saslauthd ${mech} <--- restart happens here

    # test correct credentials
    echo -n "Authentication of user ${sasluser} with correct password should succeed... "
    result=0
    output=$(testsaslauthd -u "${sasluser}" -p "${saslpass}" 2>&1) || result=$? <--- this is the authentication test

Maybe we should loop for a few times in a check for the socket, and if it still fails, add extra logging to the output so it can be troubleshooted better.

1. https://autopkgtest.ubuntu.com/packages/c/cyrus-sasl2/mantic/arm64

[Andreas Hasenack (ahasenack)]

I have a fix for this.

[Andreas Hasenack (ahasenack)]

This was fixed in debian and synced to ubuntu in https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg1-1.