| 2008-11-21 10:09:03 |
era |
bug |
|
|
added bug |
| 2008-11-21 11:03:11 |
Graham Binns |
malone: status |
New |
Incomplete |
|
| 2008-11-21 11:03:11 |
Graham Binns |
malone: statusexplanation |
|
This should be fixed when the bug watch updater checks this bug today (there can be up to a 24 hour delay between a remote bug's status changing and Launchpad pulling in the new status). I can't reproduce the problem locally so we'll wait for the bug watch to be updated in today's run before deciding whether this is actually a problem. |
|
| 2008-11-22 21:01:15 |
Graham Binns |
malone: status |
Incomplete |
Triaged |
|
| 2008-11-22 21:01:15 |
Graham Binns |
malone: assignee |
|
gmb |
|
| 2008-11-22 21:01:15 |
Graham Binns |
malone: importance |
Undecided |
High |
|
| 2008-11-22 21:01:15 |
Graham Binns |
malone: milestone |
|
2.1.12 |
|
| 2008-11-26 12:59:02 |
Graham Binns |
description |
Don't know how generalizable this is, but LP #278964 has a remote bug watch whose status is not correctly synced. Older bugs such as LP #70585 and LP #107672 seem to work correctly. |
Bug #278964 has a remote bug watch whose status is not correctly synced. Older bugs such as bug #70585 and bug #107672 seem to work correctly.
Bug 278964 was last checked by checkwatches on 2008-10-20, six days ago. Bug watches should be updated once every 24 hours or thereabouts, so this interval between checks suggests that something is going wrong with checkwatches somewhere.
Also, quite a few debbugs bug watches haven't been checked since creation (see https://bugs.edge.launchpad.net/bugs/296103/+watch/49092, which was created on 2008-11-18 and https://bugs.edge.launchpad.net/bugs/290981/+watch/48347, which was created on 2008-10-30 (!)). |
|
| 2008-11-26 12:59:02 |
Graham Binns |
title |
gnome-bugs bug watch broken? |
Bug watches aren't getting updated regularly |
|
| 2008-11-26 18:46:02 |
Graham Binns |
description |
Bug #278964 has a remote bug watch whose status is not correctly synced. Older bugs such as bug #70585 and bug #107672 seem to work correctly.
Bug 278964 was last checked by checkwatches on 2008-10-20, six days ago. Bug watches should be updated once every 24 hours or thereabouts, so this interval between checks suggests that something is going wrong with checkwatches somewhere.
Also, quite a few debbugs bug watches haven't been checked since creation (see https://bugs.edge.launchpad.net/bugs/296103/+watch/49092, which was created on 2008-11-18 and https://bugs.edge.launchpad.net/bugs/290981/+watch/48347, which was created on 2008-10-30 (!)). |
Bug #278964 has a remote bug watch whose status is not correctly synced. Older bugs such as bug #70585 and bug #107672 seem to work correctly.
Bug 278964 was last checked by checkwatches on 2008-10-20, six days ago. Bug watches should be updated once every 24 hours or thereabouts, so this interval between checks suggests that something is going wrong with checkwatches somewhere.
Also, quite a few debbugs bug watches haven't been checked since creation (see https://bugs.edge.launchpad.net/bugs/296103/+watch/49092, which was created on 2008-11-18 and https://bugs.edge.launchpad.net/bugs/290981/+watch/48347, which was created on 2008-10-30 (!)).
The problem appears to be that we don't apply a particular order to the set of bug watches that we select our batches from, so the never updated bug watches are often left un-checked whilst the have-been-updated ones are checked with more regularity.
The order should be:
1. Bug Watches never checked
2. Bug watches checked > 24 hours ago
3. Everything else.
It would be worth making the result set a UNION of (`BugWatch.lastchecked IS NULL`, `BugWatch.lastchecked > now + 24 hours`) rather than just selecting based on either of those being true. |
|
| 2008-11-26 18:46:02 |
Graham Binns |
title |
Bug watches aren't getting updated regularly |
Bug watches aren't getting updated in an ordered fashion |
|
| 2008-11-27 14:46:06 |
Graham Binns |
malone: status |
Triaged |
In Progress |
|
| 2008-11-27 14:46:06 |
Graham Binns |
malone: statusexplanation |
This should be fixed when the bug watch updater checks this bug today (there can be up to a 24 hour delay between a remote bug's status changing and Launchpad pulling in the new status). I can't reproduce the problem locally so we'll wait for the bug watch to be updated in today's run before deciding whether this is actually a problem. |
|
|
| 2008-12-17 16:41:54 |
Graham Binns |
malone: statusexplanation |
|
Didn't land this cycle due to UDS and test failures. |
|
| 2008-12-17 16:41:54 |
Graham Binns |
malone: milestone |
2.1.12 |
2.2.1 |
|
| 2009-01-21 10:21:04 |
Graham Binns |
malone: status |
In Progress |
Triaged |
|
| 2009-01-21 10:21:04 |
Graham Binns |
malone: statusexplanation |
Didn't land this cycle due to UDS and test failures. |
Moving this back to Triaged for now as there's been no significant movement on it this cycle. It's still high priority and needs to be fixed sooner rather than later. |
|
| 2009-01-29 09:09:11 |
Graham Binns |
malone: statusexplanation |
Moving this back to Triaged for now as there's been no significant movement on it this cycle. It's still high priority and needs to be fixed sooner rather than later. |
|
|
| 2009-01-29 09:09:11 |
Graham Binns |
malone: milestone |
2.2.1 |
2.2.2 |
|
| 2009-02-20 14:17:16 |
Björn Tillenius |
malone: importance |
High |
Medium |
|
| 2009-02-20 14:17:16 |
Björn Tillenius |
malone: milestone |
2.2.2 |
2.2.3 |
|
| 2009-03-02 10:44:01 |
Graham Binns |
malone: importance |
Medium |
High |
|
| 2009-03-03 10:27:17 |
Graham Binns |
malone: status |
Triaged |
In Progress |
|
| 2009-03-06 18:10:22 |
Björn Tillenius |
malone: status |
In Progress |
Fix Committed |
|
| 2009-04-02 14:41:54 |
Björn Tillenius |
malone: status |
Fix Committed |
Fix Released |
|
