| Title | Deleting fixes not replicated |
| Status | closed |
| Priority | critical |
| Assigned user | Gareth Rees |
| Organization | Perforce |
| Description | When you create a fix, the Perforce logger adds entries for the affected change and job. But when you delete a fix, the Perforce logger only adds an entry for the affected change. No entry is added for the affected job. |
| Analysis | This problem is present in the Perforce 2000.1 release. It is critical that this be fixed, otherwise the replicator won't be able to tell when fixes have been deleted from jobs (the appearance of an entry in the logger for the change is no help). So deletions of fixes won't be replicated, and so the databases will be inconsistent. For the moment I am working around this by looking at all changed jobs; this will involve replicating changes needlessly. [This is bogus. GDR 2000-11-28] This is fixed in 2000.2. See < http://info.ravenbrook.com/mail/2000/11/27/18-50-30/0.txt>. GDR also tested. RB 2000-11-28This corresponds to Perforce job job004276. |
| How found | manual_test |
| Evidence | <http://info.ravenbrook.com/mail/2000/10/03/14-59-13/0.txt> |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 10.3 |
| Created by | Gareth Rees |
| Created on | 2000-10-03 16:06:44 |
| Last modified by | Gareth Rees |
| Last modified on | 2010-10-06 21:19:33 |
| History | 2000-10-03 GDR Created. 2000-11-28 RB Tidied up. Added summary. Set priority to "critical". Closed (see analysis). |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5529 | closed | 2000-12-06 12:13:09 | Richard Brooksby | Changing the UG to reflect the "p4 submit -s" behaviour now that Perforce have fixed it. Changing the AG to insist on a particular changelevel of the server that includes that fix, in case anyone has downloaded an earlier Perforce 2000.2 beta and thinks it will work. |