We did resolve this. It turns out a copy of ssltunnel from an earlier
(failed) invocation was still running, so the (new) copy of ssltunnel
couldn't bind to its port. There were some other issues we had to sort
out as well, but eventually we got them going.
Jonathan
On 9/16/2013 12:19 PM, Gabriele Svelto wrote:
Late response but...
On 10/09/2013 19:46, Jan Jongboom wrote:
(_virtualenv)52:mochitest janjongboom$ source
../../../_virtualenv/bin/activate && python runtestsb2g.py --desktop
--console-level INFO --profile ~/repos/gaia/profile --test-path
./obj-b2g/_tests/testing/mochitest/tests/dom/permission/tests/test_keyboard.html
--app ../../../dist/B2G.app/Contents/MacOS/b2g
INFO | automation.py | Launching:
/Users/janjongboom/repos/mozilla-central-b2g/obj-b2g/dist/bin/ssltunnel
/var/folders/t8/pz9nttjd4yq8_j60t67g_5th0000gn/T/tmpp0M4Ho/ssltunnel.cfg
INFO | automation.py | SSL tunnel pid: 74298
INFO | automation.py | Launching:
/Users/janjongboom/repos/mozilla-central-b2g/obj-b2g/dist/B2G.app/Contents/MacOS/b2g
-foreground -profile
/var/folders/t8/pz9nttjd4yq8_j60t67g_5th0000gn/T/tmpp0M4Ho/
INFO | automation.py | Application pid: 74299
failed to bind socket
did you guys get around fixing this? The last time I hit this problem
it happened on a network where the DNS would return a search page
instead of an error when a non-existing domain was provided. The code
creating the server would try to look up its own address before
binding the socket and would get the webpage address instead of an
error at a certain stage. Later it would try to bind a listening
socket to this address causing the error above. If you haven't fixed
the problem already I'll open a bug and fix it because it's fairly
straightforward.
Gabriele
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
