Add a job to garbo-hourly to set next_check times for bug watches
Bug #545909 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Graham Binns | ||
Bug Description
Once the fix for bug 544943 is complete, we should add a job to garbo-hourly which takes the set of bug watches with no next_check time and calculates a next_check time for them based upon how often they've been successful over their last n BugWatchActivity entries.
If a watch has more than a certain % of recent activity entries with a failure state then it should be checked less often than one which has always succeeded or one which has only failed intermittently.
Related branches
lp:~gmb/launchpad/garbo-hourly-nextcheck-calc-bug-545909
- Gavin Panella (community): Approve
-
Diff: 409 lines (+236/-30)9 files modifieddatabase/schema/security.cfg (+2/-0)
lib/canonical/launchpad/scripts/garbo.py (+4/-25)
lib/canonical/launchpad/utilities/looptuner.py (+29/-1)
lib/lp/bugs/doc/externalbugtracker.txt (+1/-1)
lib/lp/bugs/scripts/checkwatches/__init__.py (+8/-0)
lib/lp/bugs/scripts/checkwatches/scheduler.py (+91/-0)
lib/lp/bugs/scripts/checkwatches/updater.py (+10/-0)
lib/lp/bugs/scripts/tests/test_checkwatches.py (+2/-2)
lib/lp/bugs/tests/test_bugwatch.py (+89/-1)
| Changed in malone: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
| milestone: | none → 10.03 |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in db-stable r9167 <http://