In some of our Jobs, after the Job completes, under the @tmp folder contain a folder called durable-<String> whihc contains empty file- jenkins-log.txt

The problem is that after 3 running, when we activate that job for the 4 time- we get failures like-

 java.io.IOException: CreateProcess error=267, The directory name is invalid

                at java.base/java.lang.ProcessImpl.create(Native Method)

                at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:478)

                at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:154)

                at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)

Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from

 

rg.jenkinsci.plugins.workflow.cps.CpsVmExecutorService.lambda$categoryThreadFactory$0(CpsVmExecutorService.java:50)

                                at java.base/java.lang.Thread.run(Thread.java:834)

Also:   org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 5c7a6cf3-ed16-42ec-827a-7721308f8e9f

Caused: java.io.IOException: Cannot run program "nohup" (in directory "D:\JWS\workspace\<>"): CreateProcess error=267, The directory name is invalid

                at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)

                at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)

                at hudson.Proc$LocalProc.<init>(Proc.java:252)

                at hudson.Proc$LocalProc.<init>(Proc.java:221)

                at hudson.Launcher$LocalLauncher.launch(Launcher.java:994)

                at hudson.Launcher$ProcStarter.start(Launcher.java:506)

                at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1395)

                at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1337)

                at hudson.remoting.UserRequest.perform(UserRequest.java:211)

                at hudson.remoting.UserRequest.perform(UserRequest.java:54)

                at hudson.remoting.Request$2.run(Request.java:377)

                at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)

                at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

                at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

                at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

                at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:137)

                at java.base/java.lang.Thread.run(Thread.java:834)

 

We don't know why there are leftovers under the @tmp folder at the end of the job running, but would like to see how to resolve it, or how can we use the CleanWS for the @tmp folder as well