Closed
Bug 390509
Opened 17 years ago
Closed 15 years ago
Audit Mac ref platform and check production machines
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: joduinn, Unassigned)
Details
1) We should check that all our production mac machines are using the current ref platform. 2) We should decide if we want to update/refresh the mac ref platform, like we have recently done for linux, win32.
Reporter | ||
Updated•17 years ago
|
Priority: -- → P3
Updated•17 years ago
|
Assignee: build → nobody
QA Contact: mozpreed → build
Updated•17 years ago
|
Assignee: nobody → ccooper
Comment 1•16 years ago
|
||
I'd like the unittest machines (qm-xserve02, qm-stage-osx-01) to the list of machines to be audited. Not sure how we resolve variations between build and unittest, but we should probably address that problem sooner rather than later.
Updated•16 years ago
|
Assignee: ccooper → nobody
Comment 2•16 years ago
|
||
sorry for polluting this. disregard request to audit unittest machinery. We can do that in a separate bug.
Reporter | ||
Comment 3•16 years ago
|
||
in triage: 1) not touching mozilla1.8 2) mozilla1.9: we're counting firefox mac builder as official ref standard. Need to compare thunderbird, xulrunner mac builder to make sure they are the same. 3) mozilla2 macs are confirmed to be identical, as they are all imaged from each other.
Reporter | ||
Comment 4•16 years ago
|
||
(In reply to comment #3) > 2) mozilla1.9: we're counting firefox mac builder as official ref standard. > Need to compare thunderbird, xulrunner mac builder to make sure they are the > same. Thunderbird builder going offline now, as they are moving to hg. Only XULrunner mac builder left to check here.
Component: Release Engineering → Release Engineering: Future
QA Contact: build → release
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Comment 5•14 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
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
•