Closed
Bug 859485
Opened 12 years ago
Closed 12 years ago
Cannot run B2G mochitests on desktop build. "TypeError: container is null"
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ferjm, Unassigned)
References
Details
Attachments
(1 file)
10.42 KB,
text/plain
|
Details |
I am getting this error when trying to run B2G mochitests:
Exception in thread Thread-1:
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 530, in __bootstrap_inner
self.run()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 483, in run
self.__target(*self.__args, **self.__kwargs)
File "runtestsb2g.py", line 544, in runMarionetteScript
marionette.execute_script(test_script)
File "/Volumes/SSD/dev/mozilla/mozilla-inbound/testing/marionette/client/marionette/marionette.py", line 573, in execute_script
scriptTimeout=script_timeout)
File "/Volumes/SSD/dev/mozilla/mozilla-inbound/testing/marionette/client/marionette/marionette.py", line 320, in _send_message
self._handle_error(response)
File "/Volumes/SSD/dev/mozilla/mozilla-inbound/testing/marionette/client/marionette/marionette.py", line 355, in _handle_error
raise JavascriptException(message=message, status=status, stacktrace=stacktrace)
JavascriptException: TypeError: container is null
stacktrace:
func@chrome://marionette/content/marionette-actors.js:721
@chrome://marionette/content/marionette-actors.js:726
I am running:
python runtestsb2g.py --desktop --console-level INFO --profile /data/dev/mozilla/gaia/profile/ --test-path dom/apps/tests
Attached is the full log.
Comment 1•12 years ago
|
||
This could conceivably have something to do with the B2G mochitest on mozbase refactor. We don't run B2G mochitests on the desktop build on TBPL, so breakage would be easy.
Summary: Cannot run B2G mochitests. "TypeError: container is null" → Cannot run B2G mochitests on desktop build. "TypeError: container is null"
Comment 2•12 years ago
|
||
(In reply to Jonathan Griffin (:jgriffin) from comment #1)
> This could conceivably have something to do with the B2G mochitest on
> mozbase refactor. We don't run B2G mochitests on the desktop build on TBPL,
> so breakage would be easy.
I'm not saying it's impossible, but I don't think the profile change is the cause. I did black box testing with both the old and new way of profile management and ran diffs on the files in the generated profile.
Comment 3•12 years ago
|
||
I can reproduce this locally on linux. When the tests start, I see an error on the desktop screen:
"Firefox can't find the file at app://unknown/nothing.html"
Additionally in the log I see:
!! got no appInfo for test-container.gaiamobile.org
Comment 4•12 years ago
|
||
The app://unknown/nothing.html string comes from:
http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/app/AppProtocolHandler.js#96
It looks like we are not able to successfully launch the test-container app.
Comment 5•12 years ago
|
||
I backed out http://hg.mozilla.org/mozilla-central/rev/947b9aa5e2d3 locally, and the problem disappeared. I'll look into it more tomorrow.
Comment 6•12 years ago
|
||
The problem is that with the above changeset, we no longer copy the gaia profile, so we can't launch any gaia app (like the test-container app).
Comment 7•12 years ago
|
||
Verified that things are working happily again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•