[Bug 1891403] Autopkgtest regression report (glibc/2.31-0ubuntu9.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

prometheus-blackbox-exporter/0.13.0+ds-2 (armhf, amd64, ppc64el, s390x, arm64)
prometheus-pushgateway/1.0.0+ds-1 (armhf, amd64, ppc64el, s390x, arm64)
systemd/245.4-4ubuntu3.2 (s390x, amd64, ppc64el)
gfs2-utils/unknown (amd64)
hugo/0.68.3-1 (armhf, amd64, ppc64el, s390x, arm64)
grubzfs-testsuite/0.4.10 (amd64)
glibc/2.31-0ubuntu9.1 (armhf)
badger/2.0.1-3 (armhf, amd64, ppc64el, s390x, arm64)
resource-agents/1:4.5.0-2ubuntu2 (armhf)
etcd/3.2.26+dfsg-6 (amd64, ppc64el)
postgresql-multicorn/1.3.4-31-g9ff7875-3 (armhf, amd64, ppc64el, s390x)
gfs2-utils/3.2.0-3 (ppc64el, s390x, arm64)
scipy/1.3.3-3build1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#glibc

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1891403

Title:
  glibc tst-getrandom test needs more entropy causing test failures

Status in Auto Package Testing:
  Fix Committed
Status in launchpad-buildd:
  Triaged
Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Builds and autpkgtests frequently fail due to failing tst-getrandom
  probably due to insufficient source of entropy on Launchpad. This
  causes extra work by requiring retriggering failing builds and
  autopkgtests.

  [Test Case]

  * Observe tst-getrandom tests being marked XFAIL in build logs.

  [Regression Potential]

  * The fix does not change run-time behaviour of glibc, just ignores a
  test. This lets potential breakages in getrandom()'s implementation or
  in kernel's random source being undetected, but the test results can
  still be observed in the logs if needed and the random implementation
  is also most likely exercised in other tests, too.

  [Other Info]

  The issue can be reproduced locally in a built glibc package tree
  without haveged or any other good entropy source installed:

  rbalint at gaia:~/projects/deb/build-area/glibc-2.31$ for i in $(seq 1000); do ./build-tree/amd64-libc/stdlib/tst-getrandom; done
  Timed out: killed the child process
  Termination time: 2020-08-12T21:05:28.234517252
  Last write to standard output: 2020-08-12T21:05:04.069616637
  Timed out: killed the child process
  Termination time: 2020-08-12T21:05:48.337084141
  Last write to standard output: 2020-08-12T21:05:28.069616637
  Timed out: killed the child process
  Termination time: 2020-08-12T21:06:08.439695563
  Last write to standard output: 2020-08-12T21:05:48.069616637
  Timed out: killed the child process
  Termination time: 2020-08-12T21:06:28.542962616
  Last write to standard output: 2020-08-12T21:06:08.069616637
  Timed out: killed the child process
  ...

  With haveged installed the tests pass quickly and without error:

  rbalint at gaia:~/projects/deb/build-area/glibc-2.31$ for i in $(seq 1000); do ./build-tree/amd64-libc/stdlib/tst-getrandom; done
  rbalint at gaia:~/projects/deb/build-area/glibc-2.31$

  An other way of fixing the issue would be installing better entropy
  sources in the build and autopkgtest infrastructure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1891403/+subscriptions