[JIRA] Commented: (JENKINS-7664) Exceptions when communicating with Perforce "No output for:" (probably slave-only)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-7664) Exceptions when communicating with Perforce "No output for:" (probably slave-only)

JIRA noreply@jenkins-ci.org

    [ http://issues.jenkins-ci.org/browse/JENKINS-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145809#comment-145809 ]

László Kishalmi commented on JENKINS-7664:
------------------------------------------

Well I've installed the new plugin last friday morning. Since then we did not experience any perforce "no output" related problems. This is a good sign. We keep watching it!

> Exceptions when communicating with Perforce "No output for:" (probably slave-only)
> ----------------------------------------------------------------------------------
>
>                 Key: JENKINS-7664
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-7664
>             Project: Jenkins
>          Issue Type: Bug
>          Components: perforce
>         Environment: Hudson 1.379, Perforce plugin 1.1.9
>            Reporter: torbent
>            Assignee: Rob Petti
>         Attachments: 2010-10-05-p4-no-output.txt, HUDSON-7664.diff, perforce-rpetti-54.hpi, perforce-rpetti-58.hpi, perforce.hpi
>
>
> I've seen a number of problems communicating with Perforce since upgrading to 1.1.9.
> The build log mentions "No output for: " and then a perforce command (e.g. counter/workspace). The build then fails.
> Usually the next build succeeds.
> See attached file.
> I've only seen it on slaves, i.e. remote clients.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira