[Bug 2022965] Re: ubiquity: autopkgtest fails in test_city_entry

[Robie Basak]

Hello Nick, or anyone else affected,

Accepted ubiquity into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.20 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubiquity (Ubuntu Jammy)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  ubiquity: autopkgtest fails in test_city_entry

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Won't Fix
Status in ubiquity source package in Jammy:
  Fix Committed
Status in ubiquity source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]

  The unit test in ubiquity's autopkgtest are failing for focal, jammy,
  and kinetic. This is caused by a tzdata change and has happened in the
  past, but in reverse (see bug 1951519). The current failure is:

  ======================================================================
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
      return func(*args, **keywargs)
    File "/tmp/autopkgtest.ThYxjs/build.Pwg/src/tests/test_timezone.py", line 58, in test_city_entry
      self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Canada')
  Items in the second set but not the first:
  ('Eastern', 'Bahamas')

  ----------------------------------------------------------------------
  Ran 89 tests in 10.662s

  FAILED (failures=1, skipped=1)
  autopkgtest [22:32:51]: test unit: -----------------------]
  unit                 FAIL non-zero exit status 1
  autopkgtest [22:32:52]: test unit:  - - - - - - - - - - results - - - - - - - - - -
  autopkgtest [22:32:52]: @@@@@@@@@@@@@@@@@@@@ summary
  unit                 FAIL non-zero exit status 1

  [Test Plan]

  Run autopkgtest for ubiquity.

  [Where problems could occur]

  The patch modifies expected output in a test file, so any impacts
  would be confined to running the test_city_entry unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2022965/+subscriptions