Closed Bug 936368 Opened 11 years ago Closed 10 years ago

[clock] Intermittent Travis UI Tests: TEST-UNEXPECTED-FAIL | test_clock_turn_on_off_alarm.py test_clock_turn_on_off_alarm.TestClockTurnOnOffAlarm.test_clock_turn_on_off_alarm | TimeoutException: Element edit-alarm present but not displayed before timeout

Categories

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: julienw, Assigned: zcampbell)

Details

Traceback (most recent call last):

File "/usr/local/lib/python2.7/dist-packages/marionette_client-0.6.1-py2.7.egg/marionette/marionette_test.py", line 127, in run

self.setUp()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/tests/functional/clock/test_clock_turn_on_off_alarm.py", line 19, in setUp

new_alarm = self.clock.tap_new_alarm()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/clock/app.py", line 75, in tap_new_alarm

new_alarm.wait_for_panel_to_load()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/clock/regions/alarm.py", line 64, in wait_for_panel_to_load

self.wait_for_element_displayed(*self._edit_alarm_fields_locator)

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 68, in wait_for_element_displayed

raise TimeoutException('Element %s present but not displayed before timeout' % locator)

TEST-UNEXPECTED-FAIL | test_clock_turn_on_off_alarm.py test_clock_turn_on_off_alarm.TestClockTurnOnOffAlarm.test_clock_turn_on_off_alarm | TimeoutException: Element edit-alarm present but not displayed before timeout
Also got another similar test failure:

Traceback (most recent call last):

File "/usr/local/lib/python2.7/dist-packages/marionette_client-0.6.1-py2.7.egg/marionette/marionette_test.py", line 143, in run

testMethod()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/tests/functional/clock/test_clock_add_alarm_multiple_times.py", line 29, in test_clock_add_alarm_multiple_times

new_alarm.tap_done()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/clock/regions/alarm.py", line 67, in tap_done

self.wait_for_element_displayed(*self._done_locator)

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 68, in wait_for_element_displayed

raise TimeoutException('Element %s present but not displayed before timeout' % locator)

TEST-UNEXPECTED-FAIL | test_clock_add_alarm_multiple_times.py test_clock_add_alarm_multiple_times.TestClockAddAlarmMultipleTimes.test_clock_add_alarm_multiple_times | TimeoutException: Element alarm-done present but not displayed before timeout
I think these are separate bugs but I'll have a go at comment #1 first.
Assignee: nobody → zcampbell
err comment #0 :)
On Friday I ran this several hundred times on Travis to no failure.

Comment #0 and comment #1 are different failure points and likely unrelated.

I expect the intermittent was introduced by some other change in Gaia or Gecko so this may come back at some stage, I'll keep the bug open.
This has popped up again so having another look.
Got it on another test too:

TEST-UNEXPECTED-FAIL | test_clock_set_alarm_sound.py test_clock_set_alarm_sound.TestClockSetAlarmSound.test_clock_set_alarm_sound | TimeoutException: Element edit-alarm present but not displayed before timeout
Also got:

TEST-UNEXPECTED-FAIL | test_clock_set_alarm_sound.py test_clock_set_alarm_sound.TestClockSetAlarmSound.test_clock_set_alarm_sound | ElementNotVisibleException: Element is not currently visible and may not be manipulated

Probably similar cause?
Different failure messages.
I ran this 200 times last week on Travis to not a single failures. Don't know what's going on now.

Will keep it open for a bit longer.
This test was deleted entirely hence marking wontfix.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.