java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace

Jenkins JIRA | Per Philipsen | 2 years ago
  1. 0

    Memory map plugin from Praqma does not allow to enter absolute or relative path. This is required for our build because the .cmd and .map files are found in directories relative to the Jenkins job workspace. I have tried both relative and absolute path without success. Here is an example of absolute path usage: C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>exit 0 Checking console output C:\Hudson\jobs\VALHAL_DSP_Build\builds\2014-07-10_08-50-11\log: C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>echo INFO - HUDSON_JOB_SUCCEED Memory Map Plugin version 1.0.2 java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:64) at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:42) at hudson.FilePath.act(FilePath.java:920) at hudson.FilePath.act(FilePath.java:893) at net.praqma.jenkins.memorymap.MemoryMapRecorder.perform(MemoryMapRecorder.java:100) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1735) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Printing configuration Build step 'Memory Map Publisher' changed build result to FAILURE Build step 'Memory Map Publisher' marked build as failure Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE

    Jenkins JIRA | 2 years ago | Per Philipsen
    java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace
  2. 0

    Memory map plugin from Praqma does not allow to enter absolute or relative path. This is required for our build because the .cmd and .map files are found in directories relative to the Jenkins job workspace. I have tried both relative and absolute path without success. Here is an example of absolute path usage: C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>exit 0 Checking console output C:\Hudson\jobs\VALHAL_DSP_Build\builds\2014-07-10_08-50-11\log: C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>echo INFO - HUDSON_JOB_SUCCEED Memory Map Plugin version 1.0.2 java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:64) at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:42) at hudson.FilePath.act(FilePath.java:920) at hudson.FilePath.act(FilePath.java:893) at net.praqma.jenkins.memorymap.MemoryMapRecorder.perform(MemoryMapRecorder.java:100) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1735) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Printing configuration Build step 'Memory Map Publisher' changed build result to FAILURE Build step 'Memory Map Publisher' marked build as failure Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE

    Jenkins JIRA | 2 years ago | Per Philipsen
    java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace
  3. 0

    In order to reproduce do the following steps: * Create a new buildplan (free-style project) * Source code managment: select a subversion path (doesn't matter which, just something your can check out) * Set the Check-out strategy to 'Always check out a fresh copy' * Add a 'execute shell' build script and enter the following commands: {noformat} mkdir -p a/b/c/d/e mkdir -p a/b/c/d/f touch a/b/c/d/e/1 touch a/b/c/d/e/2 touch a/b/c/d/f/1 touch a/b/c/d/f/2 ln -s ../../../../../a/b/c/d/f/1 a/b/c/d/e/4 ln -s ../../../../../a/b/c/d/f/2 a/b/c/d/e/5 ln -s ../../../../../a/b/c/d/e/1 a/b/c/d/f/4 ln -s ../../../../../a/b/c/d/e/2 a/b/c/d/f/5 chmod -R 555 a chmod 444 a/b/c/d/e/* chmod 444 a/b/c/d/f/* {noformat} Now if you launch this job, this results in the following pattern: success, fail, success, fail, ... the reason for this pattern does not immediately make sense Where a fail contains the following log: {noformat} Started by user anonymous Building on master Cleaning workspace /home/hudson/.hudson/jobs/edb-bla/workspace java.io.IOException: Unable to delete /home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e - files in dir: [/home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e/5] at hudson.Util.deleteFile(Util.java:262) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:67) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:135) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:726) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:707) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:691) at hudson.FilePath.act(FilePath.java:758) at hudson.FilePath.act(FilePath.java:740) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:633) at hudson.model.AbstractProject.checkout(AbstractProject.java:1182) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:537) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:425) at hudson.model.Run.run(Run.java:1376) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:146) Finished: FAILURE {noformat} This happens both on builds running locally as builds executed on a buildslave. Since this sometimes succeeds, this is not linked with a unix permission issue. Also, if the symlinks do not point to valid destinations then this doesn't change the story either. Now after a successful run the path looks like (excluding the svn checkout): {noformat} [hudson@mellon workspace]$ ls -Ral a a: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . drwxrwxr-x 4 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 b a/b: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 c a/b/c: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 d a/b/c/d: total 32 dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 e dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 f a/b/c/d/e: total 32 dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 .. -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 1 -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 2 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 4 -> ../../../../../a/b/c/d/f/1 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/f/2 a/b/c/d/f: total 32 dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 .. -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 1 -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 2 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 4 -> ../../../../../a/b/c/d/e/1 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/e/2 {noformat} After the failed build, it looks like this on the os: {noformat} [hudson@mellon workspace]$ ls -Ral a a: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . drwxrwxr-x 4 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 b a/b: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 c a/b/c: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 d a/b/c/d: total 24 drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. drwxr-xr-x 2 hudson hudson 4096 Jun 27 14:29 e a/b/c/d/e: total 20 drwxr-xr-x 2 hudson hudson 4096 Jun 27 14:29 . drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 .. lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/f/2 {noformat} So it managed to clean 'something' and this something is enough to make it succeed the next time. (Note, while experimenting, I've also been able to create success, fail, fail, success, fail, fail, ... patterns, I've also seen this happen when the symlinks are not valid something (e.g. omit the ../../../../'s) but since on one of my projects it failed with a symlink I introduced this in my testcase).

    Jenkins JIRA | 5 years ago | Elie De Brauwer
    java.io.IOException: Unable to delete /home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e - files in dir: [/home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e/5]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    In order to reproduce do the following steps: * Create a new buildplan (free-style project) * Source code managment: select a subversion path (doesn't matter which, just something your can check out) * Set the Check-out strategy to 'Always check out a fresh copy' * Add a 'execute shell' build script and enter the following commands: {noformat} mkdir -p a/b/c/d/e mkdir -p a/b/c/d/f touch a/b/c/d/e/1 touch a/b/c/d/e/2 touch a/b/c/d/f/1 touch a/b/c/d/f/2 ln -s ../../../../../a/b/c/d/f/1 a/b/c/d/e/4 ln -s ../../../../../a/b/c/d/f/2 a/b/c/d/e/5 ln -s ../../../../../a/b/c/d/e/1 a/b/c/d/f/4 ln -s ../../../../../a/b/c/d/e/2 a/b/c/d/f/5 chmod -R 555 a chmod 444 a/b/c/d/e/* chmod 444 a/b/c/d/f/* {noformat} Now if you launch this job, this results in the following pattern: success, fail, success, fail, ... the reason for this pattern does not immediately make sense Where a fail contains the following log: {noformat} Started by user anonymous Building on master Cleaning workspace /home/hudson/.hudson/jobs/edb-bla/workspace java.io.IOException: Unable to delete /home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e - files in dir: [/home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e/5] at hudson.Util.deleteFile(Util.java:262) at hudson.Util.deleteRecursive(Util.java:305) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.Util.deleteRecursive(Util.java:304) at hudson.Util.deleteContentsRecursive(Util.java:224) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:67) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:135) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:726) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:707) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:691) at hudson.FilePath.act(FilePath.java:758) at hudson.FilePath.act(FilePath.java:740) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:633) at hudson.model.AbstractProject.checkout(AbstractProject.java:1182) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:537) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:425) at hudson.model.Run.run(Run.java:1376) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:146) Finished: FAILURE {noformat} This happens both on builds running locally as builds executed on a buildslave. Since this sometimes succeeds, this is not linked with a unix permission issue. Also, if the symlinks do not point to valid destinations then this doesn't change the story either. Now after a successful run the path looks like (excluding the svn checkout): {noformat} [hudson@mellon workspace]$ ls -Ral a a: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . drwxrwxr-x 4 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 b a/b: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 c a/b/c: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 d a/b/c/d: total 32 dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 e dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 f a/b/c/d/e: total 32 dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 .. -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 1 -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 2 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 4 -> ../../../../../a/b/c/d/f/1 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/f/2 a/b/c/d/f: total 32 dr-xr-xr-x 2 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 4 hudson hudson 4096 Jun 27 14:27 .. -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 1 -r--r--r-- 1 hudson hudson 0 Jun 27 14:27 2 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 4 -> ../../../../../a/b/c/d/e/1 lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/e/2 {noformat} After the failed build, it looks like this on the os: {noformat} [hudson@mellon workspace]$ ls -Ral a a: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . drwxrwxr-x 4 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 b a/b: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 c a/b/c: total 24 dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 d a/b/c/d: total 24 drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 . dr-xr-xr-x 3 hudson hudson 4096 Jun 27 14:27 .. drwxr-xr-x 2 hudson hudson 4096 Jun 27 14:29 e a/b/c/d/e: total 20 drwxr-xr-x 2 hudson hudson 4096 Jun 27 14:29 . drwxr-xr-x 3 hudson hudson 4096 Jun 27 14:29 .. lrwxrwxrwx 1 hudson hudson 26 Jun 27 14:27 5 -> ../../../../../a/b/c/d/f/2 {noformat} So it managed to clean 'something' and this something is enough to make it succeed the next time. (Note, while experimenting, I've also been able to create success, fail, fail, success, fail, fail, ... patterns, I've also seen this happen when the symlinks are not valid something (e.g. omit the ../../../../'s) but since on one of my projects it failed with a symlink I introduced this in my testcase).

    Jenkins JIRA | 5 years ago | Elie De Brauwer
    java.io.IOException: Unable to delete /home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e - files in dir: [/home/hudson/.hudson/jobs/edb-bla/workspace/a/b/c/d/e/5]
  6. 0

    1. Configure a CC so it doesnt use "Use update" 2. Build once to get it working 3. Open a command prompt and go into the hudson view folder 4. Build again, which will fail as the folder can not be removed 5. Build again, now the rmview fails del path fails ---------------------------------------------- [workspace] $ cleartool rmview -force HUDSON_SHORT_CS cleartool: Error: C:\hudson\data\jobs\cc3\workspace\HUDSON_SHORT_CS: Permission denied cleartool: Error: Unable to remove the snapshot view directory. Removing view folder as it was not removed when the view was removed. FATAL: Unable to delete C:\hudson\.\data\jobs\cc3\workspace\HUDSON_SHORT_CS java.io.IOException: Unable to delete C:\hudson\.\data\jobs\cc3\workspace\HUDSON_SHORT_CS at hudson.Util.deleteFile(Util.java:148) at hudson.Util.deleteRecursive(Util.java:155) at hudson.FilePath$5.invoke(FilePath.java:342) at hudson.FilePath$5.invoke(FilePath.java:340) at hudson.FilePath.act(FilePath.java:280) at hudson.FilePath.deleteRecursive(FilePath.java:340) at hudson.plugins.clearcase.ClearToolExec.rmview(ClearToolExec.java:68) at hudson.plugins.clearcase.ClearCaseSCM.checkout(ClearCaseSCM.java:106) at hudson.model.AbstractProject.checkout(AbstractProject.java:529) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:213) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:179) at hudson.model.Run.run(Run.java:579) at hudson.model.Build.run(Build.java:103) at hudson.model.ResourceController.execute(ResourceController.java:70) at hudson.model.Executor.run(Executor.java:62) rmview fails ------------------------------------------ [workspace] $ cleartool rmview -force HUDSON_SHORT_CS cleartool: Error: Unable to open file "HUDSON_SHORT_CS\.view": No such file or directory. cleartool: Error: HUDSON_SHORT_CS isn't a view: No such file or directory cleartool: Error: Unable to remove view "HUDSON_SHORT_CS". FATAL: Clear Case failed. exit code=1 FATAL: Clear tool did not return the expected exit code. Command line="cleartool rmview -force HUDSON_SHORT_CS", actual exit code=1 java.io.IOException: Clear tool did not return the expected exit code. Command line="cleartool rmview -force HUDSON_SHORT_CS", actual exit code=1 at hudson.plugins.clearcase.ClearCaseSCM$ClearToolLauncherImpl.run(ClearCaseSCM.java:205) at hudson.plugins.clearcase.ClearToolExec.rmview(ClearToolExec.java:64) at hudson.plugins.clearcase.ClearCaseSCM.checkout(ClearCaseSCM.java:106) at hudson.model.AbstractProject.checkout(AbstractProject.java:529) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:213) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:179) at hudson.model.Run.run(Run.java:579) at hudson.model.Build.run(Build.java:103) at hudson.model.ResourceController.execute(ResourceController.java:70) at hudson.model.Executor.run(Executor.java:62)

    Jenkins JIRA | 9 years ago | redsolo
    java.io.IOException: Unable to delete C:\hudson\.\data\jobs\cc3\workspace\HUDSON_SHORT_CS

    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. java.io.IOException

      Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace

      at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke()
    2. net.praqma.jenkins
      MemoryMapConfigFileParserDelegate.invoke
      1. net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:64)
      2. net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:42)
      2 frames
    3. Hudson
      FilePath.act
      1. hudson.FilePath.act(FilePath.java:920)
      2. hudson.FilePath.act(FilePath.java:893)
      2 frames
    4. net.praqma.jenkins
      MemoryMapRecorder.perform
      1. net.praqma.jenkins.memorymap.MemoryMapRecorder.perform(MemoryMapRecorder.java:100)
      1 frame
    5. Hudson
      Executor.run
      1. hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
      3. hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
      4. hudson.model.Build$BuildExecution.post2(Build.java:182)
      5. hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
      6. hudson.model.Run.execute(Run.java:1735)
      7. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      8. hudson.model.ResourceController.execute(ResourceController.java:88)
      9. hudson.model.Executor.run(Executor.java:234)
      9 frames