997144 - Android reftest stalls with nsIHttpChannel.responseStatus NS_ERROR_NOT_AVAILABLE

Status: RESOLVED INVALID

(Testing :: Mozbase, defect)

Description

[Benoit Jacob [:bjacob] (mostly away)]

I'm trying to run reftest on Android (Nexus S, Android 2.3).

I'm making a debug, optimized build of Fennec. My host xpcshell is debug, non-optimized.

I'm using DM_TRANS=adb.

Attaching below the output of make reftest-remote.

Comment 1

[Benoit Jacob [:bjacob] (mostly away)]

Attachment: output

Comment 2

[Geoff Brown [:gbrown]]

I think that's saying that Fennec cannot see the xpcshell httpd server. Suggestions for debugging...

1. Check that the device can connect to your desktop:
    adb shell ping 10.242.37.107

2. Check that your xpcshell httpd.js is serving content. Manually start xpcshell the same way the make target does...something like: 

/hack/mozilla-central/obj-firefox-debug/dist/bin/xpcshell -g /hack/mozilla-central/obj-firefox-debug/dist/bin -v 170 -f /hack/mozilla-central/obj-mobile-debug/_tests/reftest/reftest/components/httpd.js -e "const _PROFILE_PATH = '/tmp/tmpe5Usay';const _SERVER_PORT = '8888'; const _SERVER_ADDR ='10.242.37.107';" -f /hack/mozilla-central/obj-mobile-debug/_tests/reftest/server.js

Then use a browser on your desktop to check if you can connect and get content from that server. Try to load a url like "10.242.37.107:8888". If that works, check again, manually, from a browser on your device.

3. Still not getting anywhere? We don't currently run reftests against a debug build on tbpl. I suppose there is a chance that you are encountering a Debug-specific problem -- try again with a release build.

4. For comparison, maybe try running a different set of reftests? I like TEST_PATH=layout/reftests/reftest-sanity/reftest.list

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

Thanks for the great help.

1. Yes, adb shell ping 10.242.37.107  works.

2. Yes, my xpcshell httpd is serving a directory when I browse to 10.242.37.107:8888 from my desktop. But I can't browser to 10.242.37.107:8888 from my android device, despite it being on the same wifi network and step 1. working.

3. I switched to non-DEBUG builds for both fennec and xpcshell. No difference.

4. The reftest.list is indifferent.


So it seems that my port 8888 might be blocked?  I am on the Mozilla-Guest wifi network in the Toronto office, and I am reading on the intranet now that Mozilla-Guest has some ports blocked. Can I specify a different port? How would I confirm that 8888 is blocked? At the same time, let me try to connect to 'Mozilla' with my android device.

Comment 4

[Benoit Jacob [:bjacob] (mostly away)]

I managed to connect my android device to the Mozilla wifi network now; i can again ping my computer from it; but I still can't browse to computer_ip:8888.   I don't suppose that port 8888 would be blocked on Mozilla too?

Comment 5

[Geoff Brown [:gbrown]]

I have not had trouble with 8888 being blocked, but I rarely work in an office. 

cc'ing some others that might have an idea....

Comment 6

[Benoit Jacob [:bjacob] (mostly away)]

Sorry, my linux distro (Fedora) had a firewall blocking these ports! Now that I disabled it, I can run reftest!