Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28465

WSAECONNRESET failure on sync causes build to be marked as failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: perforce-plugin
    • Labels:
    • Environment:
      Windows 7 64-bit, Jenkins 1.613, Perforce Plugin 1.3.34, P4V 2014.2/951414, P4 2014.2/943801
    • Similar Issues:

      Description

      Occasionally our project reports build failures, but when we go to look at the build output it appears that the only thing that failed was the p4 sync command. Upon running the build manually again it works fine.

      Here is the dump that all of the failures look like:

      [none] $ "C:\Program Files\Perforce\p4" -s sync -f //automated_build_sepac_main/...@204714
      Caught exception communicating with perforce. Errors encountered while force syncing: error: RpcTransport: partial message read
      error: TCP receive failed.
      error: read: socket: WSAECONNRESET
      com.tek42.perforce.PerforceException: Errors encountered while force syncing: error: RpcTransport: partial message read
      error: TCP receive failed.
      error: read: socket: WSAECONNRESET

      at com.tek42.perforce.parse.Workspaces.syncTo(Workspaces.java:167)
      at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1126)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
      at hudson.model.Run.execute(Run.java:1744)
      at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:374)
      ERROR: Unable to communicate with perforce. Errors encountered while force syncing: error: RpcTransport: partial message read
      error: TCP receive failed.
      error: read: socket: WSAECONNRESET

      Finished: FAILURE

        Attachments

          Activity

          Hide
          rpetti Rob Petti added a comment -

          I'm not seeing any problems here. The perforce plugin is correctly reporting a connectivity issue between your client and server.

          Show
          rpetti Rob Petti added a comment - I'm not seeing any problems here. The perforce plugin is correctly reporting a connectivity issue between your client and server.
          Hide
          collumbrian Brian Collum added a comment - - edited

          I guess I would expect it to possibly retry the connection again?

          Or mark the possibly mark the build as ABORTED or something similar (though I see why from your standpoint you may not want to do that).

          Either way, thanks for the help. We have been searching for the source of the problem but none of our developers have seen a issue. Only our Jenkins instance gets errors like this. But that could just be because Jenkins has lot more traffic going through it.

          Show
          collumbrian Brian Collum added a comment - - edited I guess I would expect it to possibly retry the connection again? Or mark the possibly mark the build as ABORTED or something similar (though I see why from your standpoint you may not want to do that). Either way, thanks for the help. We have been searching for the source of the problem but none of our developers have seen a issue. Only our Jenkins instance gets errors like this. But that could just be because Jenkins has lot more traffic going through it.
          Hide
          rpetti Rob Petti added a comment -
          error: RpcTransport: partial message read
          error: TCP receive failed.
          error: read: socket: WSAECONNRESET
          

          This error is directly from the perforce client, so there's really not much we can do about it. I also don't think there's a way for an SCM plugin to mark a build as anything but a failure if there's a problem...

          The best we can do is possibly add a retry, but I have personally never seen this error on any of our instances, so I suspect it's a problem with your network or your Perforce server.

          Show
          rpetti Rob Petti added a comment - error: RpcTransport: partial message read error: TCP receive failed. error: read: socket: WSAECONNRESET This error is directly from the perforce client, so there's really not much we can do about it. I also don't think there's a way for an SCM plugin to mark a build as anything but a failure if there's a problem... The best we can do is possibly add a retry, but I have personally never seen this error on any of our instances, so I suspect it's a problem with your network or your Perforce server.
          Hide
          collumbrian Brian Collum added a comment -

          Alright, well thanks for the feedback. I'll go ahead and close this.

          This will be a fun call with our IT Department...

          Show
          collumbrian Brian Collum added a comment - Alright, well thanks for the feedback. I'll go ahead and close this. This will be a fun call with our IT Department...

            People

            • Assignee:
              Unassigned
              Reporter:
              collumbrian Brian Collum
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: