Closed
Bug 1040120
Opened 10 years ago
Closed 10 years ago
[v2.1] Investigate keyboard failures when typing url
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RobertC, Unassigned)
Details
Attachments
(2 files)
Tests are failing on Jenkins when trying to type the url in the browser. From the errors it looks like the keyboard fails to switch got the correct layout.
This issue could not be reproduces locally with manual or automated tests. It looks like this is an issue in the tests.
http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame.mozilla-central.ui.functional.non-smoke/5/console
The failure occurred so far on b2g-24.2
Build info flame v2.1 (gaia info missing because of Bug 1039739):
Gecko https://hg.mozilla.org/mozilla-central/rev/a74600665875
BuildID 20140717040202
Version 33.0a1
ro.build.version.incremental=109
ro.build.date=Mon Jun 16 16:51:29 CST 2014
B1TC00011220
Traceback (most recent call last):
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/marionette_test.py", line 170, in run
testMethod()
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/tests/functional/browser/test_browser_navigation.py", line 26, in test_browser_back_button
browser.go_to_url(self.test_url)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/browser/app.py", line 47, in go_to_url
self.keyboard.send(url)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/keyboard/app.py", line 234, in send
self._switch_to_correct_layout(val)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/keyboard/app.py", line 121, in _switch_to_correct_layout
self._tap(self._numeric_sign_key)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/keyboard/app.py", line 174, in _tap
self.wait_for_element_displayed(*self._key_locator(val))
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 42, in wait_for_element_displayed
lambda m: m.find_element(by, locator).is_displayed())
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/wait.py", line 143, in until
cause=last_exc)
TimeoutException: Traceback (most recent call last):
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/wait.py", line 122, in until
rv = condition(self.marionette)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 42, in <lambda>
lambda m: m.find_element(by, locator).is_displayed())
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/marionette.py", line 1193, in find_element
response = self._send_message('findElement', 'value', **kwargs)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/decorators.py", line 35, in _
return func(*args, **kwargs)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/marionette.py", line 613, in _send_message
self._handle_error(response)
File "/var/jenkins/2/workspace/flame.mozilla-central.ui.functional.non-smoke/.env/local/lib/python2.7/site-packages/marionette_client-0.7.11-py2.7.egg/marionette/marionette.py", line 647, in _handle_error
raise errors.NoSuchElementException(message=message, status=status, stacktrace=stacktrace)
TEST-UNEXPECTED-FAIL | test_browser_navigation.py test_browser_navigation.TestBrowserNavigation.test_browser_back_button | TimeoutException: Traceback (most recent call last):
Comment 1•10 years ago
|
||
This issue is still reproducible, but only on b2g-24.2. I started adhoc runs of a test that uses keyboard, on different nodes, and the test failed only when it was ran on b2g-24.2: http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame.mozilla-b2g32_v2_0.ui.adhoc/12/console
I can't tell why is this happening, from the stacktrace it looks like the test fails when trying to switch to the correct layout.
Can someone from MV start an adhoc ran of a test that is using keyboard (E.g. test_browser_tabs.py) and make sure it is running on b2g-24.2? Then check the phone while running the test, to see how it behaves when failing. Please add all the info in this bug. Thanks!
Flags: needinfo?(dwong)
Comment 2•10 years ago
|
||
Currently at a work week, but when I have free time I will!
Flags: needinfo?(dwong)
Comment 3•10 years ago
|
||
I ran it a few times on 24.2 and once on 23.1. It seems that only on 24.2 that it accidentally taps the rocketbar causing the device to go to the search bar rather than input the url into the web browser.
Comment 4•10 years ago
|
||
Attached are two videos. One working on 23.1 and one failing on 24.2. Sorry for the shakiness:
https://drive.google.com/file/d/0BxuvwBRUSLhyQ3JwUnhBNTA2NXc/edit?usp=sharing
https://drive.google.com/file/d/0BxuvwBRUSLhyeVRTd1RkbUsyOGM/edit?usp=sharing
Comment 5•10 years ago
|
||
at 0:23 on the first video in comment #4 there is a black toaster notification from the top that says "Browser" that pops open. The tap is hitting that.
I've never seen this notification before ever and I've no idea why it would be on that device only.
Dale, do you know what this notification is?
Flags: needinfo?(dale)
Comment 6•10 years ago
|
||
I've disabled the node until we work out the problem.
Comment 7•10 years ago
|
||
Zac that is a new feature in 2.1 where the notification bar will tell you what app you are in currently, and tapping it will take you to the rocketbar search page. Any phone with mozilla central or inbound should have it I think. So it's strange that it would be a device specific bug
Comment 8•10 years ago
|
||
Dylan, can you pull that device off the grid and run the test locally and see if you can get the failure to replicate? (I've already disabled the node and the spare capacity is OK).
If you look in the logcat you should be able to get the coordinates of all the taps. You can see if the tap causing the failure is landing on the wrong cooardinates and tapping on the notification bar instead of where it's supposed to be (the keyboard) ?
Flags: needinfo?(dwong)
Comment 9•10 years ago
|
||
Clear Dale's ni? until we work out whether it's a rocketbar or Marionette or test issue.
Flags: needinfo?(dale)
Comment 11•10 years ago
|
||
Running all the browser tests locally by directly running gaiatest I saw no issues, but before running I noticed that the rocketbar would randomly open and close even after restarting. After running the tests this issue disappeared. I'm going to see if running the adhoc on it would cause the bug to happen again.
Comment 12•10 years ago
|
||
So it's not an issue of any particular test, but it seems likely to be a hardware issue. I could replace the device easily if given the word. Here is the issue occurring while the device is idle in various applications (homescreen, dialer, and browser) Most action doesn't occur until 20 seconds in:
https://drive.google.com/file/d/0BxuvwBRUSLhyZFdhTElmWEhOUm8/edit?usp=sharing
https://drive.google.com/file/d/0BxuvwBRUSLhya0Y2S3FrbmtTODA/edit?usp=sharing
I will also attach the logs for the device while idling on homescreen. I cut it off around when the rocketbar opened so more relevant information should be near the end.
Comment 13•10 years ago
|
||
I've gone ahead and replaced the device in the lab.
Attachment #8467216 -
Flags: review?(zcampbell)
Comment 14•10 years ago
|
||
Comment on attachment 8467216 [details] [review]
PR to replace device in lab
r+, you can hit merge when you've connected the device.
Attachment #8467216 -
Flags: review?(zcampbell) → review+
Comment 15•10 years ago
|
||
Comment 16•10 years ago
|
||
Running adhoc tests with the repeated tests seem to be successful, and some recent failures were due to Bug 1049582. I'm going to resolve this bug for now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•