P4DTI issue job000313

TitleIf you spell a job with the wrong case when making a fix, the replicator can't replicate it
Assigned userGareth Rees
DescriptionSuppose you have a job in Perforce called "BUG12345" and you fix it with a command like "p4 fix -c 54321 bug12345" (note the lowercase jobname). The replicator can't replicate this fix.
It generates the following error:
(P4DTI-8385) Asked for job 'bug12345' but got job 'BUG12345'.
AnalysisWe've only been able to reproduce this on a Perforce server running on Windows. It doesn't happen when the Perforce server runs on Unix.
What happens is that the Perforce server on Windows makes a "p4 logger" entry like this: "4658 job bug12345". The replicator asks for job bug12345 but it gets in return BUG12345. The replicator makes a consistency check on the output of the "p4 job" command and this fails, hence the error.
The simplest thing to do would be to make the consistency check be case-insensitive, but we also need to check the rest of the P4DTI to make sure that there aren't any other gotchas to do with case.
This is Perforce's job 5469.
How foundcustomer
Observed in1.1.1
Created byGareth Rees
Created on2001-05-05 12:30:04
Last modified byGareth Rees
Last modified on2001-12-10 19:42:29
History2001-05-05 GDR Created.


Change Effect Date User Description
12790 closed 2001-05-22 15:29:36 Gareth Rees Compare job names case-insensitively when fetching a job.