| Title | Errors from Perforce not reported well |
| Status | closed |
| Priority | essential |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | Some 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. |
| Analysis | When 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 found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dt...c/2001-01-29/release-0.5.1-test-report/>, item 6. |
| Observed in | 0.5.1 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 6.2 |
| Created by | Gareth Rees |
| Created on | 2001-02-13 15:24:58 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:22:37 |
| History | 2001-02-13 GDR Created. |