Closed Bug 821833 Opened 7 years ago Closed 7 years ago

Marionette timeout on switch_to_frame in gaia-ui-tests on desktop build

Categories

(Testing :: Marionette, defect)

x86
macOS
defect
Not set

Tracking

(firefox19 fixed, firefox20 fixed, b2g18 fixed)

RESOLVED FIXED
mozilla20
Tracking Status
firefox19 --- fixed
firefox20 --- fixed
b2g18 --- fixed

People

(Reporter: bsilverberg, Assigned: jgriffin)

Details

Attachments

(1 file)

Running tests on the latest beta desktop build (Mac 64bit) all tests timeout on switch_to_frame at https://github.com/mozilla/gaia-ui-tests/blob/master/gaiatest/gaia_test.py#L78. I went back through the older builds and found that the last working one was from 2012-12-07-03-03-24-mozilla-beta.
Can you provide the link for the current build that you've downloaded?
Ah, that's the problem.  That build is old, from Dec 10, and contained known bug which is now fixed.  We aren't building against mozilla-beta any longer, but mozilla-b2g18.  Please try a build from:

http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g18/
I just pulled down the build from latest-mozilla-b2g18 and tried it against a 'make profile' build in gaia, and I can't connect. I see:

1355519596139	Marionette	INFO	MarionetteComponent loaded
1355519596140	Marionette	INFO	marionette enabled, loadearly: false
###################################### forms.js loaded
[AccessFu] INFO attach
###################################### forms.js loaded
XXX FIXME : Got a mozContentEvent: system-message-listener-ready
1355519596974	Marionette	INFO	marionette initializing at system-message-listener-ready
XXX FIXME : Got a mozContentEvent: accessibility-screenreader
creating 1!
[TabChild] SHOW (w,h)= (0, 0)
###################################### forms.js loaded
loading app://communications.gaiamobile.org/ftu/index.html, 1
creating 1!

in the logs, so marionette is initialized.
Possibly, this is more fallout from bug 800138.  :(  I'll try to take a look soon.
I had similar problems with the nightly build, and was directed to try the beta build to address them, which was how I came across this issue.
(In reply to Jonathan Griffin (:jgriffin) from comment #5)
> Possibly, this is more fallout from bug 800138.  :(  I'll try to take a look
> soon.

This is indeed due to bug 800138, the bug that keeps on giving!  It's dying here: 
http://mxr.mozilla.org/mozilla-central/source/testing/marionette/components/marionettecomponent.js#101
This fixes the problem if you add user_pref(marionette.force-local, true); to prefs.js in Gaia's profile.
Attachment #692497 - Flags: review?(mdas)
I am available to do some more testing on this, but I'm not sure which build I should be testing. Please let me know when there is a build available to be tested and I will try again.
Attachment #692497 - Flags: review?(mdas) → review+
https://hg.mozilla.org/mozilla-central/rev/88dbe3740665
Assignee: nobody → jgriffin
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
I'm doing integration tests for the email app.

If I:

1. use last night's aurora build (http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-aurora/b2g-19.0a2.multi.linux-i686.tar.bz2),

2. and add this line to profile/user.js:

      user_pref("marionette.force-local", true);

then marionette correctly listens on port 2828 and I can run integration tests again.

This works for me now. Thank you!
You need to log in before you can comment on or make changes to this bug.