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

Too many rows scanned error after upgrading to 1.2.3

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • p4-plugin
    • None

      After upgrading to version 1.2.3 of Perforce plugin we're suddenly getting an error/exception (see below).

      This happened on two different machines after upgrading to 1.2.3. It worked happily before the upgrade and the output log didn't show any errors.

      However, when I try to do this on the command line I get the same error, so the behavior might be correct. The only thing is that it worked correct in Jenkins before the upgrade, but doesn't do it anymore after the upgrade.

      [WW] $ /usr/local/bin/p4 s sync //WW-497286900/...@34822
      Caught exception communicating with perforce. Errors encountered while syncing: error: Too many rows scanned (over 100000); see 'p4 help maxscanrows'.
      com.tek42.perforce.PerforceException: Errors encountered while syncing: error: Too many rows scanned (over 100000); see 'p4 help maxscanrows'.

      at com.tek42.perforce.parse.Workspaces.syncTo(Workspaces.java:158)
      at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:672)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1171)
      at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:521)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
      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. Errors encountered while syncing: error: Too many rows scanned (over 100000); see 'p4 help maxscanrows'.

      – Posted from Bugbox for Android

            rpetti Rob Petti
            ickersep ickersep
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: