Closed Bug 416237 Opened 12 years ago Closed 12 years ago

set up qm-pmac-fast02, qm-plinux-fast02, qm-pxp-fast02

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: anodelman, Assigned: anodelman)

References

Details

Attachments

(2 files)

These will test 1.8, the first set of fast machines is testing 1.9.
OS: Mac OS X → All
Hardware: PC → All
phong can you image one mac, one pc and one linux?
Assignee: server-ops → phong.tran
Again, the mac machine will be blocked on bug 414400 until we can resolve the image issues.
OS: All → Mac OS X
Hardware: All → PC
Bug 414400 has magically fixed itself, so all the images are ready to go.
qm-pmac-fast02	OS X 10.4.8	ym7393bgyl1	1279	ASX101-06-A-09	10.2.71.209	103.06.505	A1176
qm-pxp-fast02	Windows XP	ym7393b0yl1	1277	ASX101-06-A-11	10.2.73.212	103.06.506	A1176
qm-plinux-fast02	Ubuntu	ym7393b6yl1	1308	ASX101-06-A-13	10.2.73.220	103.06.507	A1176

Note: qm-pmac-fast02 has a 10.2.71.x address.
Assignee: phong.tran → justin
switch port changed.

btw, the switch names you  have in your spreadsheet are wrong.  Should be changed to 103-06.  pmac-fast02 is in asx103-06-C, not 101-06 (switches were mislabeled originally).
qm-pmac/plinux are done, just waiting on gni to get a kvm on pxp.  Go ahead and use the other two.
What's the timeline on getting the full set?
Can't seem to get qm-pxp-fast02 online.  mrz is heading down to the colo tomorrow morning so he'll take a look and we should be up after it's online.
Flags: needs-downtime+
Flags: needs-downtime-
Flags: needs-downtime+
Flags: colo-trip+
I'm also having trouble accessing qm-pmac-fast02, is it currently up?
Yup - I just swapped qm-pmac and qm-plinux in dns - sorry about that.  DNS is fixed (be careful you don't have the wrong IP cached).
Assignee: justin → anodelman
Status: NEW → ASSIGNED
Attachment #304548 - Flags: review?(ccooper)
qm-pxp-fast02 is up and reachable.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reopening as a core/testing bug for the buildbot work.
Status: RESOLVED → REOPENED
Component: Server Operations → Testing
Flags: needs-downtime-
Flags: colo-trip+
Product: mozilla.org → Core
Resolution: FIXED → ---
Version: other → unspecified
Comment on attachment 304548 [details] [diff] [review]
initial staging of branch fast machines

>Index: master.cfg
>===================================================================
[deletia] 
>+win32_branch_fast_builder = {
>+    'name': "WINNT 5.1 mini talos branch fast",
>+    'slavenames': ['qm-pxp--fast02'],

Looks like a typo in the slavename -> '--'

I'm assuming the BuildSteps are a carbon copy of the existing non-fast setups? r+ from me if that's the case (and with the typo fixed).
Attachment #304548 - Flags: review?(ccooper) → review+
Yup - all this stuff is pretty much copies of previous build steps that are currently up and working correctly.  Checked in with typo fixed.

Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v  <--  master.cfg
new revision: 1.36; previous revision: 1.35
done
These are up and reporting to stage.
Attachment #305875 - Flags: review?(ccooper)
Attachment #305875 - Flags: review?(ccooper) → review?(rhelmer)
Attachment #305875 - Flags: review?(rhelmer) → review+
Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v  <--  master.cfg
new revision: 1.38; previous revision: 1.37
done
Successfully reporting to Mozilla1.8
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: justin → release
Version: unspecified → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.