Closed Bug 834714 Opened 10 years ago Closed 10 years ago
_dbg _create Chrome .js in an ubuntu vm fails
FTR, This VM uses Xvfb for X.
this is blocking us from migrating over our browser chrome test. Can somebody from the developer tools team lend a hand to aid in fixing this?
I tried running the test in an Ubuntu 12.10 VirtualBox VM I have here and the test completed successfully. I ran the test using mach: ./mach mochitest-browser browser/devtools/debugger/tests/browser_dbg_createChrome.js If that is not how you ran the test, can you try this so we can see if its specific to the way you set up the environment? Comment 1 mentions using Xvfb, but it's been years since I used that, so perhaps one of you guys could save me some time by posting the steps required to do that?
you can run Xvfb like this: $ Xvfb :0 -screen 0 1600x1200x24 Generate vnc password (need tightvncserver package): $ vncpasswd Then attach x11vnc $ x11vnc -display :0 -rfbauth ~/.vnc/passwd -forever -shared Now you can VNC to that host, something like this: $ vncviewver -via $user@$host localhost
we run the tests the same way they do in automation from buildbot (i.e. there is no source tree or toolchain on the box). I download a tar.bz2 and a tests.zip file from a build directory (i.e. http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/1360077863/) I unzip them, then I run the command: python mochitest/runtests.py --appname=firefox/firefox-bin --utility-path=bin --extra-profile-file=bin/plugins --certificate-path=certs --autorun --close-when-done --console-level=INFO --symbols-path=http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/1360077863/firefox-21.0a1.en-US.linux-i686.crashreporter-symbols.zip --browser-chrome I will look at the mach command locally and see how it differs, there might be something I can do to copy all the necessary bits to the machine.
I figured this out. We are trying to setup the debuggerserver port on 6000 and that is the port that xfvb is listening on. I was able to get this test passing by changing the pref devtools.debugger.remote-port to something else (I chose 6023). Are there any concerns with my adding this new pref/setting to our automation script?
I am fine with that, thanks!
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #711926 - Flags: review?(past)
Attachment #711926 - Flags: review?(past) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 21
You need to log in before you can comment on or make changes to this bug.