DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18154>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18154 P4HandlerAdapter can throw exceptions that should be build exceptions ------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 20:52 ------- Matt, can you explain exactly in which case your patch is useful ? I have just tried to reproduce your problem with or without patch. In any case, there are no build exceptions for the case where the box where the Perforce server is living is down. Here is the verbose output for <p4label/> Build sequence for target `p4label' is [p4label] Complete build sequence is [p4label, ] p4label: [p4label] P4Label exec: [p4label] View not set, assuming //depot/... [p4label] Executing 'p4' with arguments: [p4label] 'label' [p4label] '-i' [p4label] [p4label] The ' characters around the executable and arguments are [p4label] not part of the command. [p4label] Perforce client error: [p4label] Connect to server failed; check $P4PORT. [p4label] TCP connect to 192.0.2.4:1666 failed. [p4label] connect: 192.0.2.4:1666: WSAETIMEDOUT [p4label] Executing 'p4' with arguments: [p4label] 'labelsync' [p4label] '-l' [p4label] 'NightlyBuild:20030319:2153' [p4label] [p4label] The ' characters around the executable and arguments are [p4label] not part of the command. [p4label] Perforce client error: [p4label] Connect to server failed; check $P4PORT. [p4label] TCP connect to 192.0.2.4:1666 failed. [p4label] connect: 192.0.2.4:1666: WSAETIMEDOUT
