P4DTI issue job000122

TitleServer failures aren't handled gracefully
Assigned userGareth Rees
DescriptionIf the Perforce server or the defect tracker is down, the replicator produces unhelpful error messages and e-mails to the administrator.
AnalysisThe p4 module should look at the p4 command's stderr and exit code, if possible, and raise an error if the command failed. This must then be handled by the replicator.
Really the improvement of error messages and e-mails demands a better error infrastructure. At the moment errors are undifferentiated so you can't tell what happened or what is worth logging and/or reporting in e-mail.
How foundmanual_test
EvidenceObserved during testing with RB.
Created byGareth Rees
Created on2000-12-04 18:25:27
Last modified byGareth Rees
Last modified on2001-12-10 19:09:36
History2000-12-04 GDR Created.


Change Effect Date User Description
8493 closed 2001-02-14 20:41:07 Gareth Rees Report the Perforce error message together with the exit status when we have both, so that errors aren't obscured by the exit status.
5996 open 2000-12-14 14:32:25 Richard Brooksby Fixing exit_status zero to None when there's no error.