[ 
https://issues.apache.org/jira/browse/CASSANDRA-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743869#comment-17743869
 ] 

Ekaterina Dimitrova commented on CASSANDRA-18658:
-------------------------------------------------

Good catch; we absolutely should. I looked at the test-run target where those 
are missing, too... we should probably open a ticket to update that target, too 
(or create an argument which is a concatenation of all those and use it in all 
targets... but I guess we can do that only on trunk...)
{quote}I can add that to the commit if we agree.
{quote}
Please do; thanks in advance.

> Microbench tests fail on JDK11
> ------------------------------
>
>                 Key: CASSANDRA-18658
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18658
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Marianne Lyne Manaog
>            Assignee: Marianne Lyne Manaog
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.x
>
>         Attachments: jdk11-fail.png, jdk11-pass-cass-4.0.png, 
> jdk11-pass-cass-4.1.png, jdk11-pass.png, jdk17-fail.png, jdk17-pass.png, 
> jdk8-fail.png, jdk8-pass-cass-4.0.png, jdk8-pass-cass-4.1.png, jdk8-pass.png
>
>
> When I run 
> {code:java}
> ant microbench -Dbenchmark.name=ReadWriteTest{code}
>  using jdk8 on ds-trunk, it finishes successfully, but when I run it on jdk11 
> on ds-trunk, I get this error. 
> {code:java}
> Caused by: java.lang.IllegalAccessException: access to public member failed: 
> jdk.internal.ref.Cleaner.clean[Ljava.lang.Object;@5189c629/invokeVirtual, 
> from org.apache.cassandra.io.util.FileUtils (unnamed module @6cbf4322){code}
> We suspect that ant target does not use the jvmargs as other test targets do.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to