Merge lp:~cjwatson/launchpad/schedule-bug-watches-frequently into lp:launchpad
Proposed by
Colin Watson
| Status: | Merged |
|---|---|
| Merged at revision: | 18154 |
| Proposed branch: | lp:~cjwatson/launchpad/schedule-bug-watches-frequently |
| Merge into: | lp:launchpad |
| Diff against target: |
19 lines (+1/-1) 1 file modified
lib/lp/scripts/garbo.py (+1/-1) |
| To merge this branch: | bzr merge lp:~cjwatson/launchpad/schedule-bug-watches-frequently |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| William Grant | code | Approve | |
|
Review via email:
|
|||
Commit message
Run BugWatchScheduler from garbo-frequently rather than garbo-hourly, for the sake of new watches.
Description of the change
When you create a new bug watch, it can take up to an hour for Launchpad to get round to running BugWatchScheduler so that checkwatches will check the remote bug. This seems a pretty excessive delay for something you might well be waiting for in order to make sure that it worked. BugWatchScheduler typically only takes a second or two to run, so it should be fine to run it more frequently.
To post a comment you must log in.
Revision history for this message
| William Grant (wgrant) | # |
review:
Approve
(code)
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
