Closed Bug 421385 Opened 17 years ago Closed 17 years ago

Add talos staging box (qm-plinux-stager01) to staging master

Categories

(Release Engineering :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mikeal, Unassigned)

References

Details

Attachments

(1 file, 1 obsolete file)

Attached patch staging patch 01 (obsolete) — Splinter Review
I recently setup a talos staging machine and need to get the entry checked into the master.cfg. I will need some input on the changes. Obviously the cvs checkout steps have been cut since his is intended to test code before it's been checked in. I also set it to call a script other than run_tests.py, this way it's a little more module in what we can set it to continuously run and test and aren't straddled to only testing "normal" talos runs.
Attachment #307813 - Flags: review?(rcampbell)
Attachment #307813 - Flags: review?(anodelman)
Blocks: 419105
Priority: -- → P2
Comment on attachment 307813 [details] [diff] [review] staging patch 01 This looks fine to me, though it looks like there are two instances of linux_trunk_fast_builder in the list of builders at the bottom of the patch. Also, did you mean to remove mac_branch_builder? Alice? This look good to you?
Attachment #307813 - Flags: review?(rcampbell) → review+
Attached patch staging patch 02Splinter Review
Don't know how those changes at the bottom made it in.
Attachment #307813 - Attachment is obsolete: true
Attachment #308697 - Flags: review?(rcampbell)
Attachment #308697 - Flags: review?(anodelman)
Attachment #307813 - Flags: review?(anodelman)
I don't know how those changes at the bottom crept in to the patch. The new one should be clean. -Mikeal
Nix that last patch and I'll rework for the new staging master.
Summary: Add talos staging box (qm-plinux-stager01) to perfmaster/master.cfg → Add talos staging box (qm-plinux-stager01) to staging master
Priority: P2 → P3
(reassigning to correct component, so it shows up during triage) Any update on this?
Assignee: mrogers → nobody
Component: Testing → Release Engineering: Talos
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
argh - assignment wiped when updating component...reassigning...
Assignee: nobody → mrogers
Nothing recent, I've been working my other P1 bugs. Although alice did ask me about this box, i think she was going to use it for something since i hadn't finished this task yet. Alice, are you using this box for something or should I still plan on using this VM when I get to this bug?
At the moment I'm leaving this box alone, but it could get eaten by machine requirements for branches created post ff3.
Assignee: mrogers → nobody
Alice: Could we use this machine for the staging side of the 3.next/moz2 pool? If so, whats next step here?
I'm going to re-purpose this machine as a mozilla-central nochrome tester, so nothing left to be done here. Follow up in bug 433642.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Comment on attachment 308697 [details] [diff] [review] staging patch 02 not sure what the state of this is, probably not relevant anymore. Canceling review. Housecleaning...
Attachment #308697 - Flags: review?(rcampbell)
Attachment #308697 - Flags: review?(anodelman)
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: