[Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1

[Steve Langasek]

The behavior change is because the new procps from Debian is setting an
additional sysctl setting: ./debian/protect-
links.conf:fs.protected_regular = 2

systemd in 20.04 was previously setting this to 1, which led to some
issues, discussed at https://lists.ubuntu.com/archives/ubuntu-
devel/2020-February/040904.html

No one appears to be asking for this to be set to 2, and we don't know
how many other things will be broken by this change.  We might want to
revert this in procps.

** Changed in: procps (Ubuntu)
     Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  Failed test 'default log is not used' with new procps 3.3.16-1

Status in postgresql-common package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New

Bug description:
  Since the new procps upload
   procps | 2:3.3.16-1ubuntu1   | focal-proposed  | source, amd64, arm64, armhf, i386, ppc64el, s390x
  the tests of postgresql-common fail.

  The issues are:
  autopkgtest [15:43:10]: test run-testsuite:  - - - - - - - - - - results - - - - - - - - - -
  run-testsuite        FAIL non-zero exit status 2
  autopkgtest [15:43:10]: test run-testsuite:  - - - - - - - - - - stderr - - - - - - - - - -
  #   Failed test 'default log is not used'
  #   at ./t/020_create_sql_remove.t line 143.
  #   Failed test 'default log is not used'
  #   at ./t/020_create_sql_remove.t line 154.
  # Looks like you failed 2 tests of 144.

  It was retried a few times by different people now and reproduced so
  we can assume it is a real issues for now.

  I was running two VMs to compare:
  $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img
  (and the other one without --apt-pocket=proposed=src:procps)

  The issue reproduced locally in only the one with the new procps.

  In Debian the latest similar run is
  https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz
  https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log
  But that is pre-3.3.16 and I wasn't able to find their result with the same combination.

  Lets mark this bug update-excuse and check if we can find anything in
  these VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions