ubiquity: autopkgtest fails in test_city_entry
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned |
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.
-------
Traceback (most recent call last):
File "/usr/lib/
return func(*args, **keywargs)
File "/tmp/autopkgte
self.
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]: @@@@@@@
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.
Related branches
- Steve Langasek: Approve
-
Diff: 32 lines (+5/-1)2 files modifieddebian/changelog (+4/-0)
tests/test_timezone.py (+1/-1)
Changed in ubiquity (Ubuntu): | |
status: | New → Fix Released |
Since there won't be any more point releases for focal or kinetic, it's actually not worth fixing there.