Conversation
|
@Godin Any preferences how to fix this? We probably can set a system property for those tests: Are you already on it or should I try this? I haven't seen an Ant option not to use a security manager. |
@marchof I'm on this.
And seems that I have better option 😉 will open PR after lunch. |
You're right that execution of succeeds, however addition/modification of
I was curious about this too. While was far more curious why some tests pass and some fail 😉 careful reading of failure message and test gave me a hint: line jacoco/org.jacoco.ant.test/src/org/jacoco/ant/CoverageTaskTest.xml Lines 145 to 157 in 70d5b98 the difference between these two tasks is value of Ticket https://bz.apache.org/bugzilla/show_bug.cgi?id=65381#c0 in Ant bug tracker describes the same. So my proposal is to use |
|
Thanks Evgeny, as this avoids the security manager at all for me this is the best solution. Thanks! |
|
I assume you tested this locally? The CI is still on build 18-ea+20-1248 |
Ant task `java` with parameter `fork="false"` calls `java.lang.System.setSecurityManager`, however tests should not call it, because as part of work on JEP 411 in JDK 17 it was marked as deprecated (see https://bugs.openjdk.java.net/browse/JDK-8264713) and in JDK 18 throws UnsupportedOperationException unless system property `java.security.manager` set to `allow` (see https://bugs.openjdk.java.net/browse/JDK-8270380).
yep, tested locally, |
Using
currently execution of
fails with
which is related to https://bugs.openjdk.java.net/browse/JDK-8270380
For the time being I pinned version of JDK 18 EA to b20 in Azure Pipelines to unblock processing of PRs such as #1247