There are a small, but non-zero, number of messages like this in the output:
[junit] java.security.AccessControlException: access denied
("java.io.FilePermission"
"/home/jenkins/jenkins-slave/workspace/Derby-JaCoCo/trunk/jacoco.exec"
"write")
[junit] at
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
[junit] at
java.base/java.security.AccessController.checkPermission(AccessController.java:895)
[junit] at
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:558)
[junit] at
java.base/java.lang.SecurityManager.checkWrite(SecurityManager.java:988)
[junit] at
java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:208)
[junit] at
org.jacoco.agent.rt.internal_8ff85ea.output.FileOutput.openFile(FileOutput.java:67)
[junit] at
org.jacoco.agent.rt.internal_8ff85ea.output.FileOutput.writeExecutionData(FileOutput.java:53)
[junit] at
org.jacoco.agent.rt.internal_8ff85ea.Agent.shutdown(Agent.java:137)
[junit] at
org.jacoco.agent.rt.internal_8ff85ea.Agent$1.run(Agent.java:54)
[junit] Test
org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
Perhaps something about the changes that I made to the policy files is not
quite right for the JaCoCo runs?
bryan
On Fri, Jul 6, 2018 at 3:41 PM, Rick Hillegas <rick.hille...@gmail.com>
wrote:
> Again, I'm baffled about why this jacoco cycle reported UNSTABLE results
> after successfully running to conclusion.
>
>
> -------- Forwarded Message --------
> Subject: Jenkins build is unstable: Derby-JaCoCo #313
> Date: Fri, 6 Jul 2018 21:26:47 +0000 (UTC)
> From: Apache Jenkins Server <jenk...@builds.apache.org>
> <jenk...@builds.apache.org>
> Reply-To: derby-dev@db.apache.org
> To: derby-dev@db.apache.org
>
> See
> <https://builds.apache.org/job/Derby-JaCoCo/313/display/redirect?page=changes>
>
> <https://builds.apache.org/job/Derby-JaCoCo/313/display/redirect?page=changes>
>
>
