Closed Bug 1156234 Opened 9 years ago Closed 9 years ago

Intermittent test_a11y_cards_view.py TestCardsViewAccessibility.test_a11y_cards_view | TimeoutException: TimeoutException: Timed out after 10.1 seconds

Categories

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

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

https://treeherder.mozilla.org/logviewer.html#?job_id=9048859&repo=mozilla-inbound

05:12:45 ERROR - TEST-UNEXPECTED-ERROR | test_a11y_cards_view.py TestCardsViewAccessibility.test_a11y_cards_view | TimeoutException: TimeoutException: Timed out after 10.1 seconds
05:12:45 INFO - Traceback (most recent call last):
05:12:45 INFO - File "/home/worker/build/venv/local/lib/python2.7/site-packages/marionette/marionette_test.py", line 296, in run
05:12:45 INFO - testMethod()
05:12:45 INFO - File "/home/worker/gaia/tests/python/gaia-ui-tests/gaiatest/tests/accessibility/system/test_a11y_cards_view.py", line 31, in test_a11y_cards_view
05:12:45 INFO - cards_view.wait_for_cards_view()
05:12:45 INFO - File "/home/worker/gaia/tests/python/gaia-ui-tests/gaiatest/apps/system/regions/cards_view.py", line 83, in wait_for_cards_view
05:12:45 INFO - lambda m: cards_view.get_attribute('class') == 'active')
05:12:45 INFO - File "/home/worker/build/venv/local/lib/python2.7/site-packages/marionette_driver/wait.py", line 143, in until
05:12:45 INFO - cause=last_exc)
This is a top contributor to Gip(a)'s current high failure rate. Any chance we can get someone to look into this please? :)
Component: Marionette → Gaia::UI Tests
Flags: needinfo?(gaye)
Product: Testing → Firefox OS
I'm not sure who maintains Gip right now. Moving to :davehunt who does python test stuff.
Flags: needinfo?(gaye) → needinfo?(dave.hunt)
This test tries to launch 3 apps: http://mxr.mozilla.org/gaia/source/tests/python/gaia-ui-tests/gaiatest/tests/accessibility/system/test_a11y_cards_view.py#18

Note that this kind of failure happens in a lot of other test, while trying to launch an app. There are multiple other bugs filed about this.

I guess the reason why the failure happens more frequently here is that it tries to launch 3 apps instead of 1.
This is an accessibility test, I'm not sure who is maintaining these? It looks like we're timing out waiting for an app to launch. I couldn't find a way to navigate to the Treeherder build data, which would provide a link TaskCluster build, and would allow us to see the HTML report, which might give us some clues.

Has anyone tried reproducing this locally?
Flags: needinfo?(dave.hunt) → needinfo?(eitan)
I don't know if this will remedy the timeouts, but at least we won't be switching to each app's frame? Might be worth having in master and seeing.
Flags: needinfo?(eitan)
Attachment #8616739 - Flags: review?(dave.hunt)
Comment on attachment 8616739 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/30487

I'm not against this change, but it won't impact the failures. Switching to the app frame happens after the point we're currently timing out.
Attachment #8616739 - Flags: review?(dave.hunt) → review+
I guess this is related to bug 1068094.
Depends on: 1068094
The failures are similar to bug 1161047.
(In reply to Eitan Isaacson [:eeejay] from comment #142)
> The failures are similar to bug 1161047.

Yes, there are actually many bugs like these, with intermittent failures in apps.launch. I attached a pull request in bug 1068094 that (*I think*) should fix it.
Blocks: 1174373
[Mass Closure] Closing Intermittent as a one off
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: