We don't expire old reference data (eg reference data signatures)
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P3)
Tracking
(Not tracked)
People
(Reporter: emorley, Unassigned)
References
(Blocks 1 open bug)
Details
Reporter | ||
Updated•7 years ago
|
Comment 1•5 years ago
|
||
I am interested to work on this. Kindly let me know how to proceed further for the same!
Comment 2•5 years ago
|
||
I'm looking at the data and I have no clue on how to determine what needs expiring.
I think if you take some time trying to figure out if those models are used anywhere and how they're used would be a good start.
Also look at the bugs Ed mentioned for background about this problem.
Aryx, do you have any pointers or context for this bug? Is it worth trying to fix this?
I believe investigating bug 1598433 would be a better use of your energy.
As reference, these are the models:
https://github.com/mozilla/treeherder/blob/master/treeherder/model/models.py#L1096-L1115
https://github.com/mozilla/treeherder/blob/master/treeherder/model/models.py#L284-L287
![]() |
||
Comment 3•5 years ago
|
||
Exclusion profiles got removed in bug 1387640. Have never seen that admin.html page.
Cam might have pointers if anything still needs to be removed, else WONTFIXing sounds sane.
Comment 4•5 years ago
|
||
Yeah, I don't think this bug is really valid anymore. Certainly for the reasons Aryx mentioned. But I also think we are data-cycling fairly appropriately now.
I will close this one. But I think Bug 1578195 is a better use of time. Don't remove the table, just be sure it's getting cycled properly.
Updated•5 years ago
|
Description
•