Closed
Bug 618824
Opened 14 years ago
Closed 14 years ago
Win7 xpcshell slave access
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jimm, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslaves])
I'd like to get access to a windows 7 tinderbox slave for a few days. This is in reference to bug 617503, I'm trying to figure out why our xpcshell tests run so slow. Access would be from a remote location.
Updated•14 years ago
|
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
Updated•14 years ago
|
Whiteboard: [buildduty][buildslaves]
Reporter | ||
Comment 2•14 years ago
|
||
What's the ip of the slave I should connect to? Before the break aki had me try 10.12.50.164, but I'm not able to connect to that currently. Also tried name lookups on talos-r3-w7-slave03 & talos-r3-w7-003 without success.
Reporter | ||
Comment 3•14 years ago
|
||
current name server is set to Server: mv-ns01.mv.mozilla.com Address: 10.250.0.21
Comment 4•14 years ago
|
||
Jim: talos-r3-w7-003.build.mozlila.org is the correct hostname, but it *should* only be accessible from the build network. Now that you have (temporary) build-vpn access, try logging in to build-vpn.mozilla.com. Assuming that works, port forwarding is your easiest path to victory. Something like this from your local machine: ssh -L 5900:talos-r3-w7-slave003.build.mozilla.org:5900 build-vpn.mozilla.com ...should allow you to connect to the slave via VNC.
Comment 5•14 years ago
|
||
(In reply to comment #4) > Jim: talos-r3-w7-003.build.mozlila.org is the correct hostname, but it *should* > only be accessible from the build network. talos-r3-w7-003.build.mozilla.org, ahem.
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #4) > Jim: talos-r3-w7-003.build.mozlila.org is the correct hostname, but it *should* > only be accessible from the build network. > > Now that you have (temporary) build-vpn access, try logging in to > build-vpn.mozilla.com. > > Assuming that works, port forwarding is your easiest path to victory. Something > like this from your local machine: > > ssh -L 5900:talos-r3-w7-slave003.build.mozilla.org:5900 build-vpn.mozilla.com > > ...should allow you to connect to the slave via VNC. For future reference, I ended up using putty to setup a ssh tunnel on my local port 5900 to talos-r3-w7-003.build.mozilla.org:5900. This didn't require openvpn to be setup and running.
Updated•14 years ago
|
Priority: -- → P3
Reporter | ||
Comment 7•14 years ago
|
||
All finished. I tweaked a lot of system settings on that image so it should be restored to normal state before being put into use.
Comment 9•14 years ago
|
||
Machine that had been used has been re-imaged. This bug can be closed now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•