Closed
Bug 403636
Opened 17 years ago
Closed 17 years ago
Clone unit test slaves for leak testing
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: sean)
References
Details
There seems to be some confusion in bug 397724 about cloning for leak testing, so I'm filing this bug to remove that confusion. Cloning for the staging environment is already being handled in bug 402123, but we *also* need these slave machines cloned for leak testing. This is a *separate* request for cloning/new hardware.
For leak testing, we need a clone or hardware-equiv of all the current unit testing slaves, specifically:
VMs:
* qm-centos5-01
* qm-winxp01
Phyiscal boxes (One's an Apple Xserve and the other is an HP DL360):
* qm-xserve01
* qm-win2k3-01
The VMs have already been cloned for 402123, so if you want to clone the clones for this bug, that's fine. We will need real hardware for the physical boxes here though.
Reporter | ||
Updated•17 years ago
|
Assignee: nobody → server-ops
Priority: -- → P2
Comment 1•17 years ago
|
||
Can I take the two stage VMs down to copy? And can I do that whenever?
Assignee: server-ops → mrz
Reporter | ||
Comment 2•17 years ago
|
||
mrz: yep, they are all yours.
Comment 3•17 years ago
|
||
Cloned and up at:
qm-leak-centos5-01 / 10.2.73.8
qm-leak-winxp01 / 10.2.73.7
(hostnames can change if you don't like them).
Passing to sean for the physical ones.
Assignee: mrz → sean
Assignee | ||
Comment 4•17 years ago
|
||
Machines up:
qm-leak-tiger-01 / 10.2.73.64
qm-leak-w23k-01 / 10.2.73.65
Sent login info to Coop. Resolving.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
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
•