2010-03-22 15:25:52 |
Graham Binns |
bug |
|
|
added bug |
2010-03-22 15:27:14 |
Graham Binns |
malone: status |
Triaged |
In Progress |
|
2010-03-22 15:27:17 |
Graham Binns |
malone: assignee |
|
Graham Binns (gmb) |
|
2010-03-22 15:31:24 |
Graham Binns |
branch linked |
|
lp:~gmb/launchpad/throttle-bad-watches-bug-544238 |
|
2010-03-22 15:39:34 |
Graham Binns |
malone: status |
In Progress |
Triaged |
|
2010-03-22 15:42:16 |
Graham Binns |
description |
Now that we have BugWatchActivity infrastructure we should make use of it in BugTracker.getBugWatchesNeedingUpdate(). Doing so would mean that we could throttle back updates on BugWatches whose activity shows a high percentage of failures. |
We should add a next_check column to BugWatch. This will allow us to have a garbo-hourly process that can update next_check; BugTracker.getBugWatchesNeedingUpdate() then needs only to return those watches whose next_check <= now(). |
|
2010-03-22 15:42:17 |
Graham Binns |
summary |
BugTracker.getBugWatchesNeedingUpdate() should pay attention to BugWatchActivity |
Add a next_check column to BugWatch |
|
2010-03-22 15:42:19 |
Graham Binns |
malone: status |
Triaged |
In Progress |
|
2010-03-22 15:43:28 |
Graham Binns |
branch unlinked |
lp:~gmb/launchpad/throttle-bad-watches-bug-544238 |
|
|
2010-03-22 15:45:04 |
Graham Binns |
branch linked |
|
lp:~gmb/launchpad/bugwatch-next_check-bug-544238 |
|
2010-03-23 10:45:51 |
Graham Binns |
malone: milestone |
|
10.03 |
|
2010-03-24 09:31:56 |
Graham Binns |
malone: status |
In Progress |
Fix Committed |
|
2010-03-25 08:03:12 |
Ursula Junque |
tags |
story-bug-watch-error-tracking story-reliable-bug-syncing |
qa-needstesting story-bug-watch-error-tracking story-reliable-bug-syncing |
|
2010-03-25 09:30:13 |
Graham Binns |
tags |
qa-needstesting story-bug-watch-error-tracking story-reliable-bug-syncing |
qa-ok story-bug-watch-error-tracking story-reliable-bug-syncing |
|
2010-04-05 23:03:38 |
Graham Binns |
malone: status |
Fix Committed |
Fix Released |
|