com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.

Jenkins JIRA | Sherrie Ma | 4 years ago
  1. 0

    We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference. copying a segment of the log: === Started by user admin Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev Using remote perforce client: jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 login -p [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx workspace -o jkspilot2_p4-161040911 Last build changeset: 277259 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx counter change [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s changes //jkspilot2_p4-161040911/...@277260,@277278 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx describe -s 277277 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -G where //... Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. Email was triggered for: Failure Sending email for trigger: Failure Sending email to: s@xxx.com Finished: FAILURE ===

    Jenkins JIRA | 4 years ago | Sherrie Ma
    com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.
  2. 0

    We’ve upgraded our perforce from 2012.1 to 2012.2, which supports ssl. But with the new version, the perforce plugin is having problem before the sync. It’s trying to run “p4 where” command at // level, instead of the changelist. This was a fixed bug back in 2011 in v1.2.9, which worked with the latest 2012.2. However, the newer 1.3.x won’t work. 1.3.x work fine with perforce 2012.1 with no problem. Upgraded to the latest jenkins, but no difference. copying a segment of the log: === Started by user admin Building remotely on blinnv12g in workspace /scratch/linux86/jks/perforce_test2/dev Using remote perforce client: jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 workspace -o jkspilot2_p4-161040911 [dev] $ /usr/local/bin/p4 login -p [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx workspace -o jkspilot2_p4-161040911 Last build changeset: 277259 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx counter change [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s changes //jkspilot2_p4-161040911/...@277260,@277278 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx describe -s 277277 [dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -G where //... Caught exception communicating with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Unable to communicate with perforce. P4 Where Parsing Error: Some commands just want to watch the database churn. Email was triggered for: Failure Sending email for trigger: Failure Sending email to: s@xxx.com Finished: FAILURE ===

    Jenkins JIRA | 4 years ago | Sherrie Ma
    com.tek42.perforce.PerforceException: P4 Where Parsing Error: Some commands just want to watch the database churn.
  3. 0

    Perforce Plugin - hudson - Hudson Wiki

    hudson-ci.org | 6 months ago
    com.tek42.perforce.PerforceException: No output for: p4 workspace -o SE_SCM_TEST_USER_1
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    After migrating from hudson 1.346 with perforce plugin 1.1.8 to hudson 1.379 with perforce plugin 1.1.9 I get error messages stating "PerforceException: No output for: ..." from approximately one of 4 builds. Only slave machines are affected, builds on the master work fine. Retriggering the build manually often heals the problem but is not really an option for me with about one build a minute for most of the day. I get the "No output for:" message for several commands: p4 counter change, p4 workspace -o, p4 describe, etc. Looks quite the same as issue JENKINS-7664, but I could not comment on that issue, so I had to post a separate one. Please feel free to mark this as a duplicate. {noformat} Started by upstream project "anaconda-dbtest-hamburg-limbo" build number 380 Building remotely on oehhp73k Using remote perforce client: cbuild_QS_anaconda-conversiontest-hamburg-trunk_OEHHP73L--1596120843 [anaconda-conversiontest-hamburg-limbo] $ /opt/perforce/bin/p4 workspace -o cbuild_QS_anaconda-conversiontest-hamburg-trunk_OEHHP73L--1596120843 Saving modified client cbuild_QS_anaconda-conversiontest-hamburg-trunk_OEHHP73L--1596120843 [anaconda-conversiontest-hamburg-limbo] $ /opt/perforce/bin/p4 -s client -i Last sync'd change: 306855 [anaconda-conversiontest-hamburg-limbo] $ /opt/perforce/bin/p4 counter change [anaconda-conversiontest-hamburg-limbo] $ /opt/perforce/bin/p4 -s changes //cbuild_QS_anaconda-conversiontest-hamburg-trunk_OEHHP73L--1596120843/...@306856,@307025 [anaconda-conversiontest-hamburg-limbo] $ /opt/perforce/bin/p4 describe -s 307021 Caught exception communicating with perforce. No output for: /opt/perforce/bin/p4 describe -s 307021 com.tek42.perforce.PerforceException: No output for: /opt/perforce/bin/p4 describe -s 307021 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:341) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:63) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:381) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:552) at hudson.model.AbstractProject.checkout(AbstractProject.java:1082) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) at hudson.model.Run.run(Run.java:1280) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:137) Recording test results Email was triggered for: Failure Sending email for trigger: Failure Sending email to: ...some guys... Finished: FAILURE {noformat}

    Jenkins JIRA | 6 years ago | swoyde
    com.tek42.perforce.PerforceException: No output for: /opt/perforce/bin/p4 describe -s 307021
  6. 0

    An error occurred during workspace sync which caused an exception in the plugin. Better exception handling would be required in such a case. PERFORCE OUTPUT --------------- Started by timer Building on master in workspace WORKSPACE_DIRECTORY Using master perforce client: JOB_NAME [workspace] $ p4 workspace -o JOB_NAME [workspace] $ p4 login -a -p [workspace] $ p4 -P F9151DF0014D48B57633865E55EDD343 workspace -o JOB_NAME Changing P4 Client Root to: WORKSPACE_DIRECTORY Saving modified client JOB_NAME [workspace] $ p4 -P F9151DF0014D48B57633865E55EDD343 -s client -i Note: .repository directory in workspace (if exists) is skipped during clean. Wiping workspace... Wiped workspace. Clean complete, took 0 ms Last build changeset: 289943 [workspace] $ p4 -P F9151DF0014D48B57633865E55EDD343 changes -s submitted -m 1 //JOB_NAME/... [workspace] $ p4 -P F9151DF0014D48B57633865E55EDD343 -s changes -s submitted //JOB_NAME/...@289944,@289943 Sync'ing workspace to changelist 289943 (forcing sync of unchanged files). [workspace] $ p4 -P F9151DF0014D48B57633865E55EDD343 -s sync -f //JOB_NAME/...@289943 Caught exception communicating with perforce. Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified. com.tek42.perforce.PerforceException: Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified. at com.tek42.perforce.parse.Workspaces.syncTo(Workspaces.java:167) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1111) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: Unable to communicate with perforce. Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified.

    Jenkins JIRA | 3 years ago | robsimon
    com.tek42.perforce.PerforceException: Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.tek42.perforce.PerforceException

      P4 Where Parsing Error: Some commands just want to watch the database churn.

      at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping()
    2. hudson.plugins.perforce
      PerforceSCMHelper.parseWhereMapping
      1. hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:159)
      1 frame
    3. com.tek42.perforce
      Changes.getChangelistsFromNumbers
      1. com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:82)
      2. com.tek42.perforce.parse.Changes.getChangelist(Changes.java:71)
      3. com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:425)
      3 frames
    4. hudson.plugins.perforce
      PerforceSCM.checkout
      1. hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:662)
      1 frame
    5. Hudson
      AbstractBuild$AbstractBuildExecution.defaultCheckout
      1. hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
      2 frames
    6. jenkins.scm
      SCMCheckoutStrategy.checkout
      1. jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      1 frame
    7. Hudson
      Executor.run
      1. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
      2. hudson.model.Run.execute(Run.java:1543)
      3. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      4. hudson.model.ResourceController.execute(ResourceController.java:88)
      5. hudson.model.Executor.run(Executor.java:236)
      5 frames