The scoring algorithm for build queue entries has hard-coded parameters
Bug #230330 reported by
Muharem Hrnjadovic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
The various parameters and weighting values used by the scoring algorithm for build queue entries can potentially be externalized i.e. stored apart from the code that utilizes them.
One potential advantage (?) is that these parameters could then be tweaked without the necessity to touch the scoring algorithm ..
Please note also that the lazr configuration module would be one potential repository for the parameter values in question.
Changed in soyuz: | |
status: | Incomplete → Confirmed |
Changed in soyuz: | |
importance: | Undecided → Low |
status: | Confirmed → Triaged |
To post a comment you must log in.
Muharem, you mean the values defined in score_componetname and score_urgency and the queue_time_scores?