1251782 - Explain that --disable-accessibility is unsupported on failure this causes

Status: RESOLVED FIXED

(Remote Protocol :: Marionette, defect)

Description

[Kelsey Gilbert [:jgilbert]]

`./mach mochitest` stopped working for me with these errors in the console output:
> 1456454300460   Marionette      ERROR   Error on starting server: TypeError: Ci.nsIAccessibleStates is undefined
> TypeError: Ci.nsIAccessibleStates is undefined
> @chrome://marionette/content/accessibility.js:27:3
> @chrome://marionette/content/interactions.js:12:1
> @chrome://marionette/content/driver.js:27:1
> @chrome://marionette/content/dispatcher.js:13:1
> @chrome://marionette/content/server.js:16:1
> MarionetteComponent.prototype.init@file:///c:/dev/mozilla/obj-dbg/dist/bin/components/marionettecomponent.js:185:5
> MarionetteComponent.prototype.handle@file:///c:/dev/mozilla/obj-dbg/dist/bin/components/marionettecomponent.js:102:5
...
> Traceback (most recent call last):
>   File "c:\dev\mozilla\obj-dbg\_tests\testing\mochitest\runtests.py", line 2380, in doTests
>     marionette_args=marionette_args,
>   File "c:\dev\mozilla\obj-dbg\_tests\testing\mochitest\runtests.py", line 2002, in runApp
>     self.marionette.start_session(timeout=port_timeout)
>   File "c:\dev\mozilla\gecko-dev\testing/marionette/driver\marionette_driver\marionette.py", line 1158, in start_session
>     self.protocol, _ = self.client.connect()
>   File "c:\dev\mozilla\gecko-dev\testing/marionette/driver\marionette_driver\transport.py", line 212, in connect
>     self.sock.connect((self.addr, self.port))
>   File "c:\mozilla-build-2-1-0\python\lib\socket.py", line 228, in meth
>     return getattr(self._sock,name)(*args)
> error: [Errno 10061] No connection could be made because the target machine actively refused it
> 0 ERROR Automation Error: Received unexpected exception while running application

The reason this fails seems to be that --enable-accessibility (the default) is required when building firefox. I had --disable-accessibility in my configs.

It would be helpful to surface this requirement when failures like this occur, so that people have something to try.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Yura should be able to help here.

Comment 2

[Yura Zenevich [:yzen] (please use "needinfo")]

(In reply to Henrik Skupin (:whimboo) from comment #1)
> Yura should be able to help here.

We could potentially check if 'accessibility.force_disabled' pref is set to >=1 and only then load accessibility.

Comment 3

[Yura Zenevich [:yzen] (please use "needinfo")]

(In reply to Yura Zenevich [:yzen] from comment #2)
> (In reply to Henrik Skupin (:whimboo) from comment #1)
> > Yura should be able to help here.
> 
> We could potentially check if 'accessibility.force_disabled' pref is set to
> >=1 and only then load accessibility.

Actually I would suggest trying still building with accessibility (default) and setting that pref to 1. I think it should not be enabled then.

Comment 4

[David Burns :automatedtester]

I think we should just error and tell people to build with accessibility turned on.

Comment 5

[Yura Zenevich [:yzen] (please use "needinfo")]

fixed with bug 1312816