Closed Bug 857329 Opened 11 years ago Closed 11 years ago

Scroll FPS tests are failing with 'finger is undefined'

Categories

(Remote Protocol :: Marionette, defect)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davehunt, Unassigned)

Details

Since Marionette 0.5.23 the scroll FPS tests have been failing with the following stack trace:

Traceback (most recent call last):                                                                                                                                                                                                     
  File "/Users/dhunt/workspace/b2gperf/b2gperf/b2gperf.py", line 265, in test_scrollfps
    self.scroll_app(app_name)
  File "/Users/dhunt/workspace/b2gperf/b2gperf/b2gperf.py", line 334, in scroll_app
    smooth_scroll(self.marionette, tab_dom, "y", "negative", 5000, scroll_back=True)
  File "/Users/dhunt/workspace/b2gperf/b2gperf/gestures.py", line 35, in smooth_scroll
    action.perform()
  File "/Users/dhunt/workspace/mozilla-central/testing/marionette/client/marionette/marionette.py", line 143, in perform
    self.current_id = self.marionette._send_message('actionChain', 'value', chain=self.action_chain, nextId=self.current_id)
  File "/Users/dhunt/workspace/mozilla-central/testing/marionette/client/marionette/marionette.py", line 310, in _send_message
    self._handle_error(response)
  File "/Users/dhunt/workspace/mozilla-central/testing/marionette/client/marionette/marionette.py", line 367, in _handle_error
    raise MarionetteException(message=message, status=status, stacktrace=stacktrace)
MarionetteException: finger is undefined
stacktrace:
	actions@chrome://marionette/content/marionette-listener.js:908
	actionChain@chrome://marionette/content/marionette-listener.js:989
Summary: Scroll FPS tests are failing with finger is undefined → Scroll FPS tests are failing with 'finger is undefined'
This appears to be fixed, most likely by the recent uplifted patches to b2g18.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.