[JIRA] Commented: (HUDSON-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: (HUDSON-7664) Exceptions when communicating with Perforce "No output for:" (probably slave-only)

Kohsuke Kawaguchi

    [ http://issues.hudson-ci.org/browse/HUDSON-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145029#action_145029 ]

rpetti commented on HUDSON-7664:

The latest perforce plugin should work just fine, it's only after upgrading hudson past 1.377 that the problem arises.

With kohsuke's patch, I wasn't able to reproduce the problem, but then again the rate of failure without it was only 1-2% in my tests. Others have said that the problem is still there, and that it just happens less frequently.

I doubt it's fully fixed, torbent, but if you want to help then you could try upgrading and providing a stack trace if the problem presents itself again. If your hudson deployment is mission critical, then you should probably stay at 1.377...

> Exceptions when communicating with Perforce "No output for:" (probably slave-only)
> ----------------------------------------------------------------------------------
>                 Key: HUDSON-7664
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-7664
>             Project: Hudson
>          Issue Type: Bug
>          Components: perforce
>         Environment: Hudson 1.379, Perforce plugin 1.1.9
>            Reporter: torbent
>            Assignee: rpetti
>         Attachments: 2010-10-05-p4-no-output.txt, HUDSON-7664.diff, 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.
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira