taklwu commented on pull request #3561:
URL: https://github.com/apache/hbase/pull/3561#issuecomment-895450943


   @petersomogyi  all tests passed but the jenkins job failed when ending the 
pipeline , do you know why....and do we need to fix it? 
   
   
   ```
   java.nio.file.FileSystemException: 
/home/jenkins/jenkins-agent/workspace/Base-PreCommit-GitHub-PR_PR-3561: 
Read-only file system
        at 
sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
        at 
sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
        at java.nio.file.Files.createDirectory(Files.java:674)
        at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
        at java.nio.file.Files.createDirectories(Files.java:767)
        at hudson.FilePath.mkdirs(FilePath.java:3523)
        at hudson.FilePath.access$1400(FilePath.java:213)
        at hudson.FilePath$Mkdirs.invoke(FilePath.java:1339)
        at hudson.FilePath$Mkdirs.invoke(FilePath.java:1335)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3313)
        at hudson.remoting.UserRequest.perform(UserRequest.java:211)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:375)
        at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
   ```


-- 
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