li4wang commented on PR #2352:
URL: https://github.com/apache/zookeeper/pull/2352#issuecomment-4069294678

   The pr-merge build issue seems being caused by some problem in Jenkins 
itself. 
   
   ```
   ERROR: Checkout failed
   Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to hadoop18
                at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1923)
                at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:384)
                at hudson.remoting.Channel.call(Channel.java:1112)
                at hudson.FilePath.act(FilePath.java:1228)
                at hudson.FilePath.act(FilePath.java:1217)
                at hudson.FilePath.mkdirs(FilePath.java:1408)
                at PluginClassLoader for 
git//hudson.plugins.git.GitSCM.createClient(GitSCM.java:843)
                at PluginClassLoader for 
git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1299)
                at PluginClassLoader for 
git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
                at PluginClassLoader for 
workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
                at PluginClassLoader for 
workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:101)
                at PluginClassLoader for 
workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:88)
                at PluginClassLoader for 
workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
                at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
                at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
                at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
                at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
                at java.base/java.lang.Thread.run(Thread.java:840)
   java.nio.file.FileSystemException: 
/home/jenkins/jenkins-home/workspace/eper-precommit-github-pr_PR-2352: 
Read-only file system
        at 
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
        at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
        at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
        at 
java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:397)
        at java.base/java.nio.file.Files.createDirectory(Files.java:700)
        at 
java.base/java.nio.file.Files.createAndCheckIsDirectory(Files.java:807)
        at java.base/java.nio.file.Files.createDirectories(Files.java:793)
        at hudson.FilePath.mkdirs(FilePath.java:3752)
        at hudson.FilePath$Mkdirs.invoke(FilePath.java:1418)
        at hudson.FilePath$Mkdirs.invoke(FilePath.java:1413)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3614)
        at hudson.remoting.UserRequest.perform(UserRequest.java:225)
        at hudson.remoting.UserRequest.perform(UserRequest.java:50)
        at hudson.remoting.Request$2.run(Request.java:391)
        at 
hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
   ERROR: Maximum checkout retry attempts reached, aborting
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to