hi again, didn't noted before, but this happens at analysis.a.o (came to recheck the email as analysis.apache.org/jenkins is giving an http 502 proxy error right now..)
rgrds, juan pablo On Thu, Dec 26, 2013 at 9:43 PM, Juan Pablo Santos Rodríguez < [email protected]> wrote: > Hi, > > since nearly 10 days ago jspwiki builds began to fail due to being unable > of performing a Sonar analysis. > > The build stacktraces look something like this: > [ERROR] Failed to execute goal > org.codehaus.mojo:sonar-maven-plugin:2.1:sonar (default-cli) on project > jspwiki-builder: Can not execute SonarQube analysis: Fail to extract > sonar-runner-batch.jar: Read-only file system -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.codehaus.mojo:sonar-maven-plugin:2.1:sonar (default-cli) on > project jspwiki-builder: Can not execute SonarQube analysis > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > [snip] > Caused by: org.apache.maven.plugin.MojoExecutionException: Can not execute > SonarQube analysis > at > org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:109) > [snip] > ... 19 more > Caused by: org.apache.maven.plugin.MojoExecutionException: Fail to extract > sonar-runner-batch.jar > [snip] > at > org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:104) > ... 23 more > Caused by: java.lang.IllegalStateException: Fail to extract > sonar-runner-batch.jar > at > org.sonar.runner.impl.JarExtractor.extractToTemp(JarExtractor.java:37) > at org.sonar.runner.impl.Jars35.download(Jars35.java:56) > [snip] > ... 24 more > Caused by: java.io.IOException: Read-only file system > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createTempFile(File.java:1879) > at java.io.File.createTempFile(File.java:1923) > at > org.sonar.runner.impl.JarExtractor.extractToTemp(JarExtractor.java:33) > ... 34 more > > Would anyone mind looking into this? > > Also, some of the unit tests where using an in-memory hsqldb database > running on port 9001, but these tests always failed, due to port being > used. We've changed the port to 9321, but for the sake of curiosity, is > there something running on that port? > > > thanks + br, > juan pablo >
