test_homescreen_launch_app.py: TimeoutException: TimeoutException: Timed out after 10.5 seconds

RESOLVED FIXED

Status

Firefox OS
Gaia::UI Tests
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: NicholasN, Assigned: Martijn Wargers (zombie))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Description:
This test times out some time after loading the homescreen. When manually attempting a repro, I did not have any issue launching apps from the homescreen.

Steps:
1. Update a flame device to 20150909030221.
2. Boot up the device and load the homescreen.

Actual Result:
Test times out and fails

Expected Result:
Test completes successfully.

Repro Rate: 5/5 in jenkins adhoc


Traceback (most recent call last):
File "/var/lib/jenkins/jobs/flame-kk-319.mozilla-central.nightly.ui.functional.smoke.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_client-0.17-py2.7.egg/marionette/marionette_test.py", line 277, in run
self.setUp()
File "/var/lib/jenkins/jobs/flame-kk-319.mozilla-central.nightly.ui.functional.smoke.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/tests/functional/homescreen/test_homescreen_launch_app.py", line 37, in setUp
system.wait_for_system_banner_displayed()
File "/var/lib/jenkins/jobs/flame-kk-319.mozilla-central.nightly.ui.functional.smoke.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/apps/system/app.py", line 52, in wait_for_system_banner_displayed
Wait(self.marionette).until(expected.element_displayed(*self._system_banner_locator))
File "/var/lib/jenkins/jobs/flame-kk-319.mozilla-central.nightly.ui.functional.smoke.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_driver-0.13-py2.7.egg/marionette_driver/wait.py", line 143, in until
cause=last_exc)
TimeoutException: TimeoutException: Timed out after 10.5 seconds
(Assignee)

Comment 1

3 years ago
This looks like this is happening because the system banner has changed.
Assignee: nobody → martijn.martijn
(Assignee)

Comment 2

3 years ago
I think this started failing because of bug 1202256.
Blocks: 1202256
(Assignee)

Comment 3

3 years ago
Oh, this is not simply fixed by changing the locator to gaia-toast.banner. It can find that element, but it says it's not displayed. Apparently, this makes use of webcomponents:
http://mxr.mozilla.org/gaia/source/shared/elements/gaia-component/gaia-component.js
http://mxr.mozilla.org/gaia/source/shared/elements/gaia-toast/gaia-toast.js
So we have to do some magic with shadowRoot stuff like in gaia-toast.js.
Created attachment 8659261 [details] [review]
[gaia] mwargers:1203257 > mozilla-b2g:master
(Assignee)

Comment 5

3 years ago
Comment on attachment 8659261 [details] [review]
[gaia] mwargers:1203257 > mozilla-b2g:master

Never mind, this fixes it.
The #screen > gaia-toast.banner is necessary, because outside of #screen, there are some gaia-toast.banner elements and those are always not displayed. I guess those are templates for the real element.
Attachment #8659261 - Flags: review?(npark)
Attachment #8659261 - Flags: review?(jlorenzo)
Comment on attachment 8659261 [details] [review]
[gaia] mwargers:1203257 > mozilla-b2g:master

Ah yes, I run into this many times.  It does not necessarily see the active view first when checking for the availability of the elements.  Wonder whether there is something we can do about it.  But the patch looks good
Attachment #8659261 - Flags: review?(npark) → review+
Comment on attachment 8659261 [details] [review]
[gaia] mwargers:1203257 > mozilla-b2g:master

LGTM too.
Attachment #8659261 - Flags: review?(jlorenzo) → review+
(Assignee)

Comment 8

3 years ago
Merged: https://github.com/mozilla-b2g/gaia/commit/fd04cb4eea489d5967daac8195170982c7c513e7
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.