Closed
Bug 492120
Opened 16 years ago
Closed 16 years ago
remove talos code that sends data to old graph server.
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: anodelman, Assigned: anodelman)
References
Details
Attachments
(1 file)
16.41 KB,
patch
|
catlee
:
review+
anodelman
:
checked-in+
|
Details | Diff | Splinter Review |
Once we switch full time to the new graph server we will no longer be supporting the old send protocol.
Assignee | ||
Comment 1•16 years ago
|
||
Attachment #377574 -
Flags: review?(catlee)
Comment 2•16 years ago
|
||
Comment on attachment 377574 [details] [diff] [review]
[Checked in]pull out code from talos that supports the old graph server
I love removing code!
Attachment #377574 -
Flags: review?(catlee) → review+
Assignee: anodelman → nobody
Component: Release Engineering: Talos → Release Engineering
Updated•16 years ago
|
Assignee: anodelman → nobody
Updated•16 years ago
|
Assignee: nobody → anodelman
Assignee | ||
Comment 3•16 years ago
|
||
Waiting on downtime for rollout.
Assignee | ||
Comment 4•16 years ago
|
||
Comment on attachment 377574 [details] [diff] [review]
[Checked in]pull out code from talos that supports the old graph server
Checking in PerfConfigurator.py;
/cvsroot/mozilla/testing/performance/talos/PerfConfigurator.py,v <-- PerfConfigurator.py
new revision: 1.12; previous revision: 1.11
done
Checking in run_tests.py;
/cvsroot/mozilla/testing/performance/talos/run_tests.py,v <-- run_tests.py
new revision: 1.47; previous revision: 1.46
done
Attachment #377574 -
Attachment description: pull out code from talos that supports the old graph server → [Checked in]pull out code from talos that supports the old graph server
Attachment #377574 -
Flags: checked-in+
Assignee | ||
Comment 5•16 years ago
|
||
Successfully rolled out in Tuesday morning downtime.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
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
•