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

Exceptions when communicating with Perforce "No output for:" (probably slave-only)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • None
    • Hudson 1.379, Perforce plugin 1.1.9

      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.

        1. 2010-10-05-p4-no-output.txt
          2 kB
        2. HUDSON-7664.diff
          2 kB
        3. perforce.hpi
          295 kB
        4. perforce-rpetti-54.hpi
          299 kB
        5. perforce-rpetti-58.hpi
          305 kB

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

          jonasbovin added a comment -

          Looks like I jumped the gun earlier, when running it more frequently I can achieve as much as 80% successes and 20% "no output error".
          Hope this helps.

          jonasbovin added a comment - Looks like I jumped the gun earlier, when running it more frequently I can achieve as much as 80% successes and 20% "no output error". Hope this helps.

          Rob Petti added a comment -

          If anyone still able to reproduce this problem would care to try the attached build. I've made a minor change that will hopefully do the trick. perforce-rpetti-54.hpi

          Rob Petti added a comment - If anyone still able to reproduce this problem would care to try the attached build. I've made a minor change that will hopefully do the trick. perforce-rpetti-54.hpi

          jonasbovin added a comment - - edited

          rpetti: I've tried the perforce-rpetti-54.hpi on a 1.394 Hudson, but unfortunately it just hangs after:

          ...
          Using master perforce client: HudsonWebTestClient
          --[workspace] $ "C:\Program Files\Perforce\p4.exe" workspace -o HudsonWebTestClient

          never gets beyond the workspace command - usually what happens is that it fails - as it is not logged in and then issues the login statement an gets a ticket (see below):

          When using the 1.1.14 plugin which every now and then get 'No output...'
          Using master perforce client: HudsonWebTestClient
          --[workspace] $ "C:\Program Files\Perforce\p4.exe" workspace -o HudsonWebTestClient
          --[workspace] $ "C:\Program Files\Perforce\p4.exe" login -p
          --[workspace] $ "C:\Program Files\Perforce\p4.exe" -P 20DADC12CB3FEA1432C78D34E289BAB2 workspace -o HudsonWebTestClient
          Last sync'd change: 183801

          When I try to cancel the hanging job, it resumes next line as above on 1.1.14 plugin. This also affects non-slaves, master will also hang until job is canceled manually from Hudson web-interface.

          Using remote perforce client: HudsonSlaveWebTestClient--1608677735
          [SlaveAutotestHelper] $ "C:\Program Files\Perforce\p4.exe" workspace o HudsonSlaveWebTestClient-1608677735 (first halted, then I canceled job manually)
          [SlaveAutotestHelper] $ "C:\Program Files\Perforce\p4.exe" login -p (haltes, then I canceled job manually)
          Caught exception communicating with perforce. Unable to login via p4 login due to IOException: nullcom.tek42.perforce.PerforceException: Unable to login via p4 login due to IOException: null
          at com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:488)
          at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:350)
          at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53)
          at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1081)
          at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:541)
          at hudson.model.AbstractProject.checkout(AbstractProject.java:1171)
          at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:480)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:412)
          at hudson.model.Run.run(Run.java:1362)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:145)
          ERROR: Unable to communicate with perforce. Unable to login via p4 login due to IOException: null
          Finished: FAILURE

          jonasbovin added a comment - - edited rpetti: I've tried the perforce-rpetti-54.hpi on a 1.394 Hudson, but unfortunately it just hangs after: ... Using master perforce client: HudsonWebTestClient -- [workspace] $ "C:\Program Files\Perforce\p4.exe" workspace -o HudsonWebTestClient never gets beyond the workspace command - usually what happens is that it fails - as it is not logged in and then issues the login statement an gets a ticket (see below): When using the 1.1.14 plugin which every now and then get 'No output...' Using master perforce client: HudsonWebTestClient -- [workspace] $ "C:\Program Files\Perforce\p4.exe" workspace -o HudsonWebTestClient -- [workspace] $ "C:\Program Files\Perforce\p4.exe" login -p -- [workspace] $ "C:\Program Files\Perforce\p4.exe" -P 20DADC12CB3FEA1432C78D34E289BAB2 workspace -o HudsonWebTestClient Last sync'd change: 183801 When I try to cancel the hanging job, it resumes next line as above on 1.1.14 plugin. This also affects non-slaves, master will also hang until job is canceled manually from Hudson web-interface. Using remote perforce client: HudsonSlaveWebTestClient--1608677735 [SlaveAutotestHelper] $ "C:\Program Files\Perforce\p4.exe" workspace o HudsonSlaveWebTestClient -1608677735 (first halted, then I canceled job manually) [SlaveAutotestHelper] $ "C:\Program Files\Perforce\p4.exe" login -p (haltes, then I canceled job manually) Caught exception communicating with perforce. Unable to login via p4 login due to IOException: nullcom.tek42.perforce.PerforceException: Unable to login via p4 login due to IOException: null at com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:488) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:350) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:53) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1081) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:541) at hudson.model.AbstractProject.checkout(AbstractProject.java:1171) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:480) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:412) at hudson.model.Run.run(Run.java:1362) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) ERROR: Unable to communicate with perforce. Unable to login via p4 login due to IOException: null Finished: FAILURE

          seanhoughton added a comment -

          I tried 1.1.15 and got the same result: hang on the workspace command. With 1.1.14 I get the "no output" problem 3 out of 12 times.

          I'm fully willing to keep trying beta versions if you keep posting them. Alternatively, my email is "shoughton at highmoonstudios.com".

          seanhoughton added a comment - I tried 1.1.15 and got the same result: hang on the workspace command. With 1.1.14 I get the "no output" problem 3 out of 12 times. I'm fully willing to keep trying beta versions if you keep posting them. Alternatively, my email is "shoughton at highmoonstudios.com".

          Rob Petti added a comment -

          I was able to reproduce the problem (or one strikingly similar) and was able to fix it by reimplementing the remote calls performed by the plugin. Can someone else test it? (perforce-rpetti-58.hpi)

          If it works for others, then I'll release it and update JENKINS-7809 with my findings.

          Rob Petti added a comment - I was able to reproduce the problem (or one strikingly similar) and was able to fix it by reimplementing the remote calls performed by the plugin. Can someone else test it? ( perforce-rpetti-58.hpi ) If it works for others, then I'll release it and update JENKINS-7809 with my findings.

          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!

          László Kishalmi added a comment - 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!

          Rob, I'm eagerly waiting for your findings wrt JENKINS-7809!

          Kohsuke Kawaguchi added a comment - Rob, I'm eagerly waiting for your findings wrt JENKINS-7809 !

          Rob Petti added a comment -

          Work around released in perforce plugin version 1.2.0.

          Rob Petti added a comment - Work around released in perforce plugin version 1.2.0.

          torbent added a comment -

          That's SO great! This means I may finally move on from Hudson 1.377 – to Jenkins, naturally

          torbent added a comment - That's SO great! This means I may finally move on from Hudson 1.377 – to Jenkins, naturally

          torbent added a comment -

          This issue started on Hudson, and our Hudson installation is actually still at 1.377 because of it. We've since moved some of our jobs to Jenkins and haven't seen the slightest trace of this problem, so I think it's (about) time to close it.

          torbent added a comment - This issue started on Hudson, and our Hudson installation is actually still at 1.377 because of it. We've since moved some of our jobs to Jenkins and haven't seen the slightest trace of this problem, so I think it's (about) time to close it.

            rpetti Rob Petti
            torbent torbent
            Votes:
            18 Vote for this issue
            Watchers:
            27 Start watching this issue

              Created:
              Updated:
              Resolved: