[Bug 1510060] Re: test regression: TestCloneUpgrade.test_clone_upgrade_synthetic

[Christian Ehrhardt ]

FTR this is back in Hirsute and seems it was back bug force-badtested in focal& groovy.
See bug 1902830

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

Title:
  test regression: TestCloneUpgrade.test_clone_upgrade_synthetic

Status in apt-clone package in Ubuntu:
  Invalid

Bug description:
  apt-clone's tests have worked fine in wily
  (http://autopkgtest.ubuntu.com/packages/a/apt-clone/wily/amd64/) but
  started failing consistently in xenial
  (http://autopkgtest.ubuntu.com/packages/a/apt-clone/xenial/amd64/).

  This can be reproduced fast in a simple schroot with the test deps
  installed:

  $ cd tests; PYTHONPATH=.. python3 test_clone_upgrade.py -v TestCloneUpgrade.test_clone_upgrade_synthetic
  [...]
  ======================================================================
  FAIL: test_clone_upgrade_synthetic (__main__.TestCloneUpgrade)
  test clone upgrade with on-the-fly generated chroots
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "test_clone_upgrade.py", line 58, in test_clone_upgrade_synthetic
      self.assertTrue(len(cache.get_changes()) > 0)
  AssertionError: False is not true

  I added
              print('--------- %s -----\n%s\n-------------' % (meta, cache.get_changes()))

  to the test, and I get

  --------- ubuntu-standard -----
  []
  --------- ubuntu-desktop -----
  [<Package: name:'libvisual-0.4-plugins' architecture='amd64' id:6857>]
  --------- kubuntu-desktop -----
  [<Package: name:'libvisual-0.4-plugins' architecture='amd64' id:6857>, <Package: name:'lksctp-tools' architecture='amd64' id:9362>]
  --------- xubuntu-desktop -----
  [<Package: name:'libvisual-0.4-plugins' architecture='amd64' id:6857>]
   
  So the check works for the metapackages except ubuntu-standard. More curiously, when running the test on wily *now*, it also fails, which suggests that perhaps the very late distro-info update for xenial may have influenced this?

  But I haven't the slightest idea what this test is trying to do, so I
  don't know how to fix this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/1510060/+subscriptions