Closed Bug 792650 Opened 12 years ago Closed 11 years ago

cfx test randomly fails on android

Categories

(Add-on SDK Graveyard :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: evold, Assigned: jsantell)

Details

I occasionally get the following error while using cfx test w/ and android device:

(jetpack-sdk)evold-10775:addon-kit evold$ cfx test -a fennec-on-device -b ~/android/android-sdk-macosx/platform-tools/adb --mobile-app fennec --force-mobile -v -f tabs
Launching mobile application with intent name org.mozilla.fennec
Pushing the addon to your device
Starting: Intent { act=android.activity.MAIN cmp=org.mozilla.fennec/.App (has extras) }
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
Could not read chrome manifest 'file:///data/data/org.mozilla.fennec/chrome.manifest'.
zerdatime 1348104747730 - browser chrome startup finished.
Reader: Init()
[AccessFu] INFO attach
OpenGL LayerManager Initialized Succesfully.
Version: OpenGL ES 2.0 14.01002
Vendor: NVIDIA Corporation
Renderer: NVIDIA Tegra 3
FBO Texture Target: TEXTURE_2D
could not find host for about:home, [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.host]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/browser.js :: isMarketplace :: line 6193"  data: no]
Reader: parseDocumentFromTab: 1
Reader: Not parsing URI scheme: about
###!!! ABORT: We need a context on Android: file ../../../gfx/layers/opengl/LayerManagerOGL.cpp, line 175
###!!! ABORT: We need a context on Android: file ../../../gfx/layers/opengl/LayerManagerOGL.cpp, line 175

I see a crash screen on Fennec on my android.  The screen says a crash report was sent to Mozilla, and I have the option to close or restart, so I just close and try again and it usually works.
It could be somehow related to bug 806813, bug 806815 and bug 806817. The "ABORT" message is the same, and I got it always (not occasionally) if I run one of tests mentioned in the bugs. A way to reproduce the error is run the following test (at least on Samsung Galaxy Tab 10.1 with Firefox Mobile 16.0):

cfx test -a fennec-on-device -b ~/android-sdk-macosx/platform-tools/adb  --force-mobile -v -f test-content-proxy:testTypedArraysX
Assignee: nobody → jsantell
All tests passing, closing for now, can track future specific bugs
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.