Closed
Bug 1144686
Opened 9 years ago
Closed 6 years ago
test_settings_change_time_format consistently failing, seems to revert the time set
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: njpark, Unassigned)
References
Details
(Whiteboard: [3.0-Daily-Testing])
+++ This bug was initially created as a clone of Bug #1141654 +++ The test (test_settings_change_time_format.py) is failing with about 80% repro rate. The new reason for failure is due to the issues seen in bug 1085652. The time set in the script will be reset to a different time value when Date & Time page is opened, and 'Set Automatically' is enabled. I think the reason this test was passing so far was that on previous builds it took some time to reset the time, but now I notice it happens within 1~2 seconds. In order to fix this, either 1) the marionette command to set the time should persist even the Date & Time page is opened, or 2) one should set the time after the Date & Time page is opened. OR, 3) the time change should be done via the UI interaction. I'll check out how 2) works as a quick fix for now.
Reporter | ||
Updated•9 years ago
|
Depends on: 1141654
Summary: test_settings_change_time_format consistently failing, seems to hang and fail on the homescreen → test_settings_change_time_format consistently failing, seems to revert the time set
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 1•9 years ago
|
||
Just found out there is a new settings bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1144713 Probably should disable this test case until it is fixed.
Depends on: 1144713
(In reply to No-Jun Park [:njpark] from comment #1) > Just found out there is a new settings bug: > https://bugzilla.mozilla.org/show_bug.cgi?id=1144713 > Probably should disable this test case until it is fixed. I agree. 80% repro means we probably should have disabled it by now anyway.
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•