1225324 - test_sms_report.py : TimeoutException: TimeoutException: Timed out after 300.0 seconds

Status: RESOLVED DUPLICATE of bug 1225180

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

Description

[Max Ivanov[:MaxIvanov]]

Description: Test case fails with "TimeoutException"

Steps:
1. Update a flame device to 20151116030435
2. Run this test case http://lxr.mozilla.org/gaia/source/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_report.py

Actual result:
"TimeoutException"

Expected result:
Test completes successfully.

Repro Rate: Reproduced via Jenkins adhoc (0/5 passing)
http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.ui.adhoc.bitbar/344/HTML_Report/

Traceback (most recent call last):
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_client-1.0.0-py2.7.egg/marionette/marionette_test.py", line 296, in run
testMethod()
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_report.py", line 28, in test_sms_report
self.message_thread.wait_for_received_messages()
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/apps/messages/regions/message_thread.py", line 25, in wait_for_received_messages
*self._received_message_content_locator))))
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_driver-1.0.0-py2.7.egg/marionette_driver/wait.py", line 143, in until
cause=last_exc)
TimeoutException: TimeoutException: Timed out after 300.0 seconds

Comment 1

[Johan Lorenzo [:jlorenzo]]

The report shows 2 things:
* At the beginning we had this error
> AssertionError: u'gaia706151 test' != u'[phone]'
which is due to another test saving this number as a contact. The memory will be cleared by bug 1225180.
* Then the timeout error. This error is weird. We already had received message so the wait condition should have passed even without waiting on another message to come. My guess is that we hit a race condition in our test, which won't happen anymore with bug 1225180.