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


** Changed in: cyrus-sasl2 (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021505

Title:
  Flaky DEP8 test: saslauthd

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2021505/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to