[Bug 1869364] Re: glibc pwd/test-getpw test failures in autopkgtest

[Launchpad Bug Tracker]

This bug was fixed in the package glibc - 2.31-0ubuntu9.1

---------------
glibc (2.31-0ubuntu9.1) focal; urgency=medium

  [ Michael Hudson-Doyle ]
  * Mark tst-getpw as XFAIL on arm64. (LP: #1869364)

  [ Matthias Klose ]
  * Copy the fully conditionalized x86 variant for math-vector-fortran.h
    to /usr/include/finclude. On all architectures. (LP: #1879092)

  [ Balint Reczey ]
  * debian/gbp.conf: Add initial configuration
  * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository
  * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER
    (LP: #1889190)
  * Fall back to calling nanosleep syscall when __clock_nanosleep returns
    EINVAL due to CLOCK_REALTIME not being supported (LP: #1871129)
  * debian/testsuite-xfail-debian.mk: XFAIL tst-getpw on armhf, too
    (LP: #1869364)
  * XFAIL stdlib/tst-getrandom (LP: #1891403)

  [ Dimitri John Ledkov ]
  * debian/patches/powerpc: Cherrypick upstream patches to support POWER10
    optimized library loading. LP: #1887989

 -- Balint Reczey <rbalint at ubuntu.com>  Mon, 17 Aug 2020 22:02:52 +0200

** Changed in: glibc (Ubuntu Focal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1869364

Title:
  glibc pwd/test-getpw test failures in autopkgtest

Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Focal:
  Fix Released
Status in glibc source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  pwd/test-getpw test fails in autopkgtest
  Fixing this makes the arm64 and armhf autopkgtests usable again for the lifetime of the 20.04 LTS release.

  [Test Case]

  Observe autopkgetest tests passing, including pwd/test-getpw being
  marked as XFAIL.

  [Regression Potential]

  The fix is ignoring a test failure due to the problems explained in
  the bug comments. The fix does not affect run-time behaviour.

  [Original Bug Text]

  I started seeing this in the testing for 5.4.0-20. Only happening on
  arm64/armhf.

  ----------
  FAIL: pwd/tst-getpw
  original exit status 223
  PASS: NULL buffer returns -1 and sets errno to EINVAL.
  PASS: Read a password line given a uid.
  FAIL: Did not find even one invalid uid.
  ----------

  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/g/glibc/20200326_165114_2fcf9@/log.gz
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/g/glibc/20200326_173356_3378d@/log.gz

  I've unsuccessfully tried to reproduce this on an arm64 host (by
  running this test case standalone, not the full test suite), so
  possibly there's something about the autopkgtest environment. This
  also happens with the 5.4.0-18 from focal-release, so it does not
  appear to be a regression in the kernel.

  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/arm64/g/glibc/20200326_224201_5fd33@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1869364/+subscriptions