[
https://issues.apache.org/jira/browse/CASSANDRA-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742125#comment-17742125
]
Ekaterina Dimitrova commented on CASSANDRA-18658:
-------------------------------------------------
{code:java}
This PR is not against a branch we have, but this is simple to cherry-pick on
commit.
{code}
That branch is on top of 4.0, not trunk, where many changes were made in
build.xml lately, many around JDK and args.
[~marianne-manaog], please create PR and test against OSS C* trunk? Also, I
suggest adding the
{code:java}
<jvmarg line="${java17-jvmargs}"/>{code}
too.
Thank you in advance.
Looking at build.xml, we might want to add also:
{code:java}
<jvmarg line="${_std-test-jvmargs11}" />
<jvmarg line="${_std-test-jvmargs17}" />{code}
And, if we want it to still work with J8, J11, and J17, we might need to add at
the end also
{code:java}
<jvmarg line="${test.jvm.args}" />{code}
> 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: ReadWriteTest-Fail.png, ReadWriteTest-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]
