Closed
Bug 722894
Opened 13 years ago
Closed 13 years ago
Move testfailure-caching updating to separate script
Categories
(Tree Management Graveyard :: OrangeFactor, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcote, Unassigned)
Details
Attachments
(1 file)
10.06 KB,
patch
|
jgriffin
:
review+
|
Details | Diff | Splinter Review |
Right now the testfailures call normally returns cached data, but with the updatecache=1 parameter, it retrieves the data and caches it. It is intended that a cron job use this parameter periodically.
We should move this to a script and get rid of the updatecache parameter because this is a memory-intensive task. Separating it will (a) move the memory to the client script, which need not be on the same machine as the server, and (b) prevent random users from triggering this action.
Assignee | ||
Comment 1•13 years ago
|
||
Also moved some hard-coded config variables into a config file; see orangefactor.conf.example.
Attachment #593246 -
Flags: review?(jgriffin)
Comment 2•13 years ago
|
||
Comment on attachment 593246 [details] [diff] [review]
Moved testfailures cache updating to separate script
Looks good after a pretty cursory review!
Attachment #593246 -
Flags: review?(jgriffin) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Pushed as http://hg.mozilla.org/automation/orangefactor/rev/0486482b2f77. Server deployed; going to run the script to update the cache from flyingtanks.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Testing → Tree Management
Updated•4 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•