P4DTI issue job000202

TitleErrors from Perforce not reported well
Assigned userGareth Rees
DescriptionSome Perforce errors are reported only as "The Perforce client exited with error code %d. Is the server down or the server address incorrect?" This provides little help in tracking down the problem.
AnalysisWhen the exit code of the p4 client is non-zero, then the above error message is produced, regardless of whether there was a Perforce error message.
The p4 module should use both pieces of information (the Perforce error and the exit code).
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dt...c/2001-01-29/release-0.5.1-test-report/>, item 6.
Observed in0.5.1
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 6.2
Created byGareth Rees
Created on2001-02-13 15:24:58
Last modified byGareth Rees
Last modified on2001-12-10 19:22:37
History2001-02-13 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.