Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the 
subtest "tests-in-lxd" would be related to some fstab issues in those issues. 
But recently all architectures, but s390x recovered. I assume that the fstab 
issue is fixed but something else surfaces now.

groovy
  s390x
    tests-in-lxd                   (F 100% f  0% S  0% B  0% => P  0%/) 
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    boot-and-services              (F  3% f  0% S  0% B  0% => P 96%/) 
.....F........................
    systemd-fsckd                  (F 26% f 73% S  0% B  0% => P  0%/) 
ffffffffffffffffffffFFFFfFFfFF

We see when systemd-fsckd was marked flaky (F->f), but tests-in-lxd
continues to perma-stop any migration depending on systemd.

Currently this holds back a lot of things in groovy, it seems to be:
qemu/1:5.0-5ubuntu7 chiark-tcl/1.3.4ubuntu3 cmake-extras/1.5-1ubuntu1 
cstore-fdw/1.7.0-1 dateparser/0.7.4-1 dpdk/19.11.4-1 gem2deb/1.2.1 
glibc/2.32-0ubuntu2 gnome-desktop3/3.37.90.1-1ubuntu1 grep/3.4-1 
libnss-nis/3.1-0ubuntu3 libnss-nisplus/1.3-0ubuntu3 link-grammar/5.8.0-1 
mksh/59b-1 natsort/7.0.1-1 openconnect/8.10-1 orafce/3.13.4-1 
pandas/1.0.5+dfsg-3 pango1.0/1.46.1-1 php-nesbot-carbon/2.32.2-1 
php-shellcommand/1.6.1-1 php-twig/2.13.0-1 postgresql-12/12.4-1 
postgresql-common/216 postgresql-multicorn/1.4.0-2 reprotest/0.7.15 
snapd/2.46.1+20.10 symfony/4.4.11+dfsg-1ubuntu1 systemd/246.4-1ubuntu1 
tracker/2.3.4-1build1 vis/0.6-3

Therefore re-opening the groovy task, this isn't over yet :-/
@rbalint please let us know if you know more details about it already.

** Changed in: systemd (Ubuntu)
       Status: Fix Released => New

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd                   (F 42% S  0% B 10% => P 45%/) 
FFFFBFFFFFFFB....FF.B.....F.....F...FBF
  build-login                    (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  unit-config                    (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  networkd-testpy                (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  boot-and-services              (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  boot-smoke                     (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  logind                         (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  storage                        (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  upstream                       (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFB....FF.B.....F.F..F....FBF
  udev                           (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
  systemd-fsckd                  (F 37% S  0% B 10% => P 50%/) 
FFFFBFFFFFFFB.FF...FB.....F..........B.
  root-unittests                 (F  0% S  0% B 10% => P 87%/) 
....B.......B.......B................B.
    ppc64el
  tests-in-lxd                   (F 25% S  0% B  0% => P 75%/) 
FFFF....FF............FFF.....F.........
  systemd-fsckd                  (F 35% S  0% B  0% => P 65%/) 
FFFFFFF...FF........F....FF.F..F........
  root-unittests                 (F  2% S  0% B  0% => P 97%/) 
..............................F.........
    s390x
  tests-in-lxd                   (F 52% S  0% B  0% => P 47%/) 
FFFFFFF.FFFFFFF.FF.........FFFF...F.....
  timedated                      (F  2% S  0% B  0% => P 97%/) 
...........F............................
  upstream                       (F 17% S  0% B  0% => P 82%/) 
.....F......F.F.............FFF...F.....
  systemd-fsckd                  (F 32% S  0% B  0% => P 67%/) 
FFFFFFF..FF..F.................FF..F....
  root-unittests                 (F 10% S  0% B  0% => P 90%/) 
............................FFF...F.....
    arm64
  tests-in-lxd                   (F 40% S  0% B  2% => P 57%/) 
FFFFF.B...FFF.FF..F..F.........FFF.F....
  logind                         (F  2% S  0% B  2% => P 95%/) 
......B...................F.............
  upstream                       (F 22% S  0% B  2% => P 75%/) 
...F.FB.....F.F.............F..FFF.F....
  root-unittests                 (F 12% S  0% B  2% => P 85%/) 
......B.F...........F.F........F...F....

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+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