autopilot tests fail when run in UTC+1 timezone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Calendar App |
Confirmed
|
High
|
Unassigned |
Bug Description
All the calendar_
Traceback (most recent call last):
File "/home/
self.
File "/home/
self.
File "/home/
Eventually(
File "/usr/lib/
raise mismatch_error
MismatchError: After 10.0 seconds test failed: 12 != 11
This is because in _assert_today(), self.month_
currentMonth should be converted to the current timezone before using it.
Related branches
- Ubuntu Phone Apps Jenkins Bot: Needs Fixing (continuous-integration)
- Ubuntu Calendar Developers: Pending requested
-
Diff: 97 lines (+9/-10)4 files modifiedtests/autopilot/calendar_app/tests/test_dayview.py (+4/-4)
tests/autopilot/calendar_app/tests/test_monthview.py (+1/-1)
tests/autopilot/calendar_app/tests/test_weekview.py (+3/-4)
tests/autopilot/calendar_app/tests/test_yearview.py (+1/-1)
- Ubuntu Phone Apps Jenkins Bot: Approve (continuous-integration)
- Nicholas Skaggs (community): Approve
-
Diff: 182 lines (+43/-21)5 files modifiedtests/autopilot/calendar_app/emulators.py (+6/-0)
tests/autopilot/calendar_app/tests/test_dayview.py (+4/-4)
tests/autopilot/calendar_app/tests/test_monthview.py (+19/-9)
tests/autopilot/calendar_app/tests/test_weekview.py (+13/-7)
tests/autopilot/calendar_app/tests/test_yearview.py (+1/-1)
Changed in ubuntu-calendar-app: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ubuntu-calendar-app: | |
status: | Triaged → In Progress |
assignee: | nobody → Kunal Parmar (pkunal-parmar) |
Changed in ubuntu-calendar-app: | |
status: | Fix Committed → Fix Released |
So if we use the utc datetime, does this solve everything? It should like the property we receive is in UTC, so we can use UTC time to do an assert against it.