946665 - Bad intermittent on Travis with `test_keyboard_basic`

Status: RESOLVED WONTFIX

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

Description

[Zac C (:zac)]

This is failing with a very high intermittent rate on Travis.

We need this addressed urgently.


-------------------

TEST-START test_keyboard.py

test_keyboard_basic (test_keyboard.TestKeyboard) ... ERROR

======================================================================

ERROR: None

----------------------------------------------------------------------

Traceback (most recent call last):

File "/usr/local/lib/python2.7/dist-packages/marionette_client-0.6.2-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/keyboard/test_keyboard.py", line 42, in test_keyboard_basic

contact_details = contacts_app.contacts[0].tap()

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/contacts/app.py", line 112, in tap

return ContactDetails(self.marionette)

File "/home/travis/build/mozilla-b2g/gaia/tests/python/gaia-ui-tests/gaiatest/apps/contacts/regions/contact_details.py", line 22, in __init__

self.wait_for_condition(lambda m: m.find_element(*self._contact_name_title_locator).location['x'] == 0)

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

raise TimeoutException(message)

TEST-UNEXPECTED-FAIL | test_keyboard.py test_keyboard.TestKeyboard.test_keyboard_basic | TimeoutException: Condition timed out

Comment 1

[Zac C (:zac)]

Attachment: github pr

Comment 2

[Trif Andrei-Alin[:AlinT]]

Comment on attachment 8343145 [details] [review]
github pr

r+

Comment 3

[Trif Andrei-Alin[:AlinT]]

Merged in:
https://github.com/mozilla-b2g/gaia/commit/270b28855124e6885ec0c835909d43465c7412bb

Comment 4

[Trif Andrei-Alin[:AlinT]]

v1.2 affected

Comment 5

[Michael Henretty [:mikehenrty][:mhenretty]]

Can we xfail this test until we figure this out? It's making Travis very hard to use as a sanity check before landing.

Comment 6

[Zac C (:zac)]

Hi Michael I see this is failing for a completely different reason now and it is affecting two tests that "tap add new contact"

If you want to disable it then do that rather than xfail, otherwise we will fix it up properly first thing on Monday.

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=947620 to track it as it's a different issue.

Comment 7

[Michael Henretty [:mikehenrty][:mhenretty]]

Thanks Zac, sounds good. We will probably disable the test in the meantime to try and get travis green so we can open the tree again.

By the way, not sure if you saw the mailing list, but there was also a gecko regression and a bunch of other intermittent failures piling up today. Gregor is sorting through them, poor guy, but he may end up disabling a bunch of tests in the meantime.

https://groups.google.com/d/msg/mozilla.dev.gaia/3KkVWP-LKBc/K9aC_gz5XacJ

Comment 8

[Anthony Ricaud (:rik)]

This bug as been disabled in https://github.com/mozilla-b2g/gaia/commit/bfc00fb75030f89af41a1408c6799f67c510a208 to reopen the tree.

Comment 9

[Florin Strugariu [:Bebe]]

hmm this is strange :D

When I run the test if you change focus from the simulator to a new window the keyboard disappears
also 
why do we do this?
https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/keyboard/test_keyboard.py#L23

Use send keys to open the keyboard instead of tapping on the element?

Comment 10

[Dave Hunt [:davehunt] [he/him] ⌚BST]

(In reply to Florin Strugariu [:Bebe] from comment #9)
> When I run the test if you change focus from the simulator to a new window
> the keyboard disappears

Are you including the --app=b2gdesktop command line argument? This enabled focus manager test mode, and is necessary for running tests of the desktop client.

Comment 11

[Florin Strugariu [:Bebe]]

Yes Dave but if we switch focus from the b2g window to something else when the keyboard is typing that the test fails.

Comment 12

[Zac C (:zac)]

Bebe that's not the problem here. Look at the stacktrace, the problem is not related to that.

Comment 13

[Bob Silverberg [:bsilverberg]]

Is Travis still running for v1.2? If so, is this intermittent also happening on v1.2? If neither of those are true then we should remove the status-b2g-v1.2: affected flag.

Comment 14

[Zac C (:zac)]

I checked the last week of v1.2 Travis jobs (about 1 per day) and there was no evidence of this intermittent.

This was one of a bunch around the same time that showed evidence of some kind of notification shrouding the buttons at the top of the page. I'm fairly sure this one has gone away.

Comment 15

[Zac C (:zac)]

Seems stable now.