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

Ubuntu SRU Bot 1871129 at bugs.launchpad.net
Mon Sep 14 15:02:17 UTC 2020


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

Title:
  htop is blank when using in focal in wsl1

Status in Ubuntu WSL:
  In Progress
Status in glibc package in Ubuntu:
  Fix Released
Status in htop package in Ubuntu:
  Invalid
Status in glibc source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Programs previously using nanosleep syscall and with glibc 31's update
  being switched to use clock_nanosleep broke due to clock_nanosleep
  using CLOCK_REALTIME returns EINVAL in wsl1.

  [Test Case]

  Run sleep in WSL1 on Windows 10 2004 or older version.
  The fixed version works correctly, the not fixed version breaks in Focal.

  Run the following program under in WSL1 and on a real kernel with
  strace and observe that the fallback is applied only when it is
  needed:

  #include <time.h>
  #include <stdio.h>

  int main (int argc, char ** argv) {
   struct timespec ts, rem;
         clock_gettime(CLOCK_REALTIME, &ts);
   printf("Sleep 1.5s with TIMER_ABSTIME\n");
   ts.tv_nsec += 500000000L;
   if (ts.tv_nsec > 1000000000L) {
    ts.tv_nsec -= 1000000000L;
      ts.tv_sec += 1;
   }
   ts.tv_sec += 1;
   clock_nanosleep(CLOCK_REALTIME, TIMER_ABSTIME, &ts, &rem);

   printf("sleep 1.2s\n");
   ts.tv_sec = 1;
   ts.tv_nsec = 200000000L;
   clock_nanosleep(CLOCK_REALTIME, 0, &ts, &rem);

   printf("sleep 1.2s with CLOCK_MONOTONIC\n");
   ts.tv_sec = 1;
   ts.tv_nsec = 200000000L;
   clock_nanosleep(CLOCK_MONOTONIC, 0, &ts, &rem);

   printf("invalid sleep -1s (+200ms)\n");
   ts.tv_nsec = 200000000L;
   ts.tv_sec = -1;
   clock_nanosleep(CLOCK_REALTIME, 0, &ts, &rem);

   printf("invalid sleep 1s (-200ms)\n");
   ts.tv_nsec = -200000000L;
   ts.tv_sec = 1;
   clock_nanosleep(CLOCK_REALTIME, 0, &ts, &rem);

   printf("invalid sleep 0s (+1.200ms as nsec)\n");
   ts.tv_nsec = 1200000000L;
   ts.tv_sec = 1;
   clock_nanosleep(CLOCK_REALTIME, 0, &ts, &rem);

  }

  [Regression Potential]

  The fix is falling back to using monotonic time and also converts the clock_nanosleep call to not use TIMER_ABSTIME in the fallback.
  If the calculation from absolute to relative time is not correct then it may result in a very long sleep effectively hanging the calling process.
  Also the checks in the callback can crash the calling program if a mistake is made.
  The program in the [Test] section aims to cover all branches of the fix.

  [Original Bug Text]

  Right now I am trying Ubuntu 20.04 on WSL and I noticed that when I
  run htop in WSL 1st generation, it is completely blank:

  https://user-images.githubusercontent.com/15316889/78563857-31697b00
  -784e-11ea-9f21-338a6cf8cb23.gif

  The previous version (htop 2.1.0) works without any issue.

  I am using htop 2.2.0-2build1 on Ubuntu 20.04 on WSL1 on Windows 10
  build 19592.1001.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuwsl/+bug/1871129/+subscriptions



More information about the foundations-bugs mailing list