Closed
Bug 432732
Opened 17 years ago
Closed 16 years ago
have talos results be machine independant
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: anodelman, Unassigned)
Details
Currently, talos results are strongly tied to individual machines. If we could be assured that the result of any single talos machine would be the same as that reported for the same tests on the same build on a different machine we'd be able to do some nice things like machine sharing and easier replacement of dead boxes.
We are already using images to get us to the same initial state on different boxes, but it doesn't seem to be enough to get us to totally standard results.
Comment 1•16 years ago
|
||
Results are much improved since doing auto-rebooting after each run.
We still occasionally get a machine returning results that are drifting away from results from other machines. Typically, a complete o.s. reimage fixes this - unknown whats the cause of this.
Comment 2•16 years ago
|
||
Alice sez:
14:38 < alice> bhearsum: i had though that i already closed that
14:39 < alice> we are basically already assuming that they are machine
independant
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 3•15 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•