Closed
Bug 393068
Opened 17 years ago
Closed 17 years ago
create talos slaves to evaluate old pageloader vs. new
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
I will be doing this on qm-mini-xp01 and 02.
Assignee | ||
Updated•17 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•17 years ago
|
||
qm-mini-xp01 is up and running with the old pageloader and reporting to graphs-stage for now. I seem to be missing some files for the new pageloader, so that's stuck until I get them from vlad or alice.
Assignee | ||
Comment 2•17 years ago
|
||
I got the files I needed for the new pageloader. Both of these are up and running, reporting to graphs-stage. Buildbot seems to get a bit mixed up and try to pull the wrong files sometimes. Still looking into this.
Assignee | ||
Comment 3•17 years ago
|
||
The aforementioned bug has been fixed.
Assignee | ||
Comment 4•17 years ago
|
||
Alice,
We've made the decision to use the new pageloader once Talos2 is checked in, right? Are we still going to evaluate the different pageloaders on Mac and Linux?
Summary: create two win32 talos slaves to evaluating old pageloader vs. new → create talos slaves to evaluate old pageloader vs. new
Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 5•16 years ago
|
||
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: 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
•