Closed
Bug 947881
Opened 12 years ago
Closed 12 years ago
ReferenceError: GaiaDataLayer is not defined
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Bebe, Unassigned)
References
Details
Attachments
(1 file)
346.88 KB,
text/plain
|
Details |
Some of the tests running on both v1.2 and mozilla-central are failing with:
JavascriptException: ReferenceError: GaiaDataLayer is not defined
Failing tests on master and v1.2:
test_camera_capture_video.py
test_export_contacts_to_sdcard.py
test_dialer.py
test_settings_change_language.py
test_settings_gps.py
test_settings_do_not_track.py
test_settings_bluetooth.py
test_settings_cell_data.py
test_settings_passcode.py
These are reproducing on hamachi only we can't see the fails on Inaris
http://qa-selenium.mv.mozilla.com:8080/job/b2g.hamachi.mozilla-central.ui/379/
http://qa-selenium.mv.mozilla.com:8080/job/b2g.hamachi.mozilla-b2g26_v1_2.ui/
Using:
hamachi-eng-mozilla Builds from Dec 8, 2013
Reporter | ||
Comment 1•12 years ago
|
||
Stack trace example:
File "/var/jenkins/workspace/b2g.hamachi.mozilla-central.ui/tests/python/gaia-ui-tests/gaiatest/gaia_test.py", line 330, in active_telephony_state
return self.marionette.execute_script("return GaiaDataLayer.getMozTelephonyState()")
File "/var/jenkins/workspace/b2g.hamachi.mozilla-central.ui/.env/local/lib/python2.7/site-packages/marionette_client-0.6.2-py2.7.egg/marionette/marionette.py", line 1025, in execute_script
filename=os.path.basename(frame[0]))
File "/var/jenkins/workspace/b2g.hamachi.mozilla-central.ui/.env/local/lib/python2.7/site-packages/marionette_client-0.6.2-py2.7.egg/marionette/marionette.py", line 577, in _send_message
self._handle_error(response)
File "/var/jenkins/workspace/b2g.hamachi.mozilla-central.ui/.env/local/lib/python2.7/site-packages/marionette_client-0.6.2-py2.7.egg/marionette/marionette.py", line 612, in _handle_error
raise JavascriptException(message=message, status=status, stacktrace=stacktrace)
JavascriptException: ReferenceError: GaiaDataLayer is not defined
stacktrace:
execute_script @gaia_test.py, line 330
inline javascript, line 0
src: "let __marionetteFunc = function(){return GaiaDataLayer.getMozTelephonyState()};__marionetteFunc.apply(null, __marionetteParams);"
Comment 2•12 years ago
|
||
I'm unable to reproduce this locally on any of the mentioned tests against hamachi with the following build.
Gaia: 1d45d1dc3201059d5c8f2efdeb92c04576d8e161
Gecko: http://hg.mozilla.org/mozilla-central/rev/0204febd3146
BuildID 20131209040204
Version 28.0a1
Comment 3•12 years ago
|
||
Related to bug 948193, perchance? Also GaiaDataLayer code, but fails to return the right value, elsewhere.
Comment 4•12 years ago
|
||
(Was still happening as of this morning's build, too: http://qa-selenium.mv.mozilla.com:8080/job/b2g.hamachi.mozilla-central.ui/383/) We'll see what the next build yields.
Comment 5•12 years ago
|
||
This is not occurring at all on Taipei Jenkins server.
Comment 6•12 years ago
|
||
I checked again using:
Gecko revision: http://hg.mozilla.org/mozilla-central/rev/1ad9af3a2ab8
Gaia is: https://github.com/mozilla-b2g/gaia/commit/8952898bbc98dd31e25b647203791cf129867ff1
1) I created and have been running this job off and on: http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.ui.gpsStephend/
2) I've attached its logcat
Still happening :-(
Comment 7•12 years ago
|
||
Updated•12 years ago
|
Severity: normal → major
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Comment 8•12 years ago
|
||
1) So, http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.ui/374/ was good too, on the 6th of December, with only 1 unrelated failure
2) Looks like when we picked up that day's build: http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.ui/375/, we started seeing this issue.
Comment 9•12 years ago
|
||
I just tried replicating this on b2g-2 (it has replicated on this device) without success. The only difference is that b2g-2 was not in a good state when I connected so I had to remotely flash it. Once done, I ran all of the problematic tests without failure...
Comment 10•12 years ago
|
||
Interestingly, after switching to the non-RIL builds and a new flash script, it looks like these issues have gone away. Maybe this is related to a bad flash, though I'm not sure how...
Before switch: http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.ui/402/consoleFull
After switch: http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.ui/405/consoleFull
I don't know what the cause was(is?), either, but, as Dave says in comment 10, and it shows, this looks "fixed," to me. Marking as WFM because it is, and I don't have a commit to point to.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•