| Title | Consistency check may complain about Bugzilla bugs which are OK |
| Status | closed |
| Priority | optional |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If one touches an old Bugzilla bug (one which has not been changed since the start_date), using the 'commit' button in the Bugzilla GUI, the replicator starts replicating it. If that bug is then changed from Perforce but not from Bugzilla, the consistency checker check.py will complain that there is no such issue (e.g. "Job 'bug5' is marked as being replicated to issue '5' but that issue either doesn't exist or is not being replicated by this replicator."). |
| Analysis | The 'commit' button only updates the delta_ts; it doesn't write to bugs_activity or p4dti_bugs_activity. Updating from Perforce then writes to bugs_activity, p4dti_bugs_activity and the delta_ts. So this bug then looks as if all its actvity since the start_date is p4dti_bugs_activity, so all_bugs_since() doesn't return it.
I think dt_bugzilla.all_issues() really wants to call something other than bugzilla.all_bugs_since(). |
| How found | manual_test |
| Evidence | Testing on 1.0.5. |
| Observed in | 1.0.5 |
| Introduced in | 0.5.0 |
| Created by | Nick Barnes |
| Created on | 2001-03-21 15:33:01 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:33:35 |
| History | 2001-03-21 NB Created. |