[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694778#comment-17694778
]
Ekaterina Dimitrova edited comment on CASSANDRA-18106 at 2/28/23 11:22 PM:
---------------------------------------------------------------------------
What I noticed is that the number of failures is different between 30 and 40 so
they are flaky tests. The issue is only with JDK11 but we didn't change the
image, introducing newer JDK or the jolokia jar that the DTest repo comes with.
I started digging further and I noticed you probably give rerun to the workflow
from the UI? Is this correct?
Could it be anything else get cached?
I did another test now - pushed on my end a branch with your ccm repo and I ran
into different problem:
This was trying on an 11 build to run the tests with 8 -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2312/workflows/f7c3bf3f-b3f0-4ab0-82c8-408866dd363c/jobs/18973
This is your commit to your branches on latest trunk.
Then on the same branch with trunk and the current ccm without your branch I
didn't notice that problem:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2313/workflows/0df1adfb-bf74-4477-86d1-bb4830d8d697/jobs/18976
(I cancelled both builds but if you scroll through the steps)
Can you try to trigger your branch by pushing empty commit? I think what you
see is probably cached ccm maybe?
was (Author: edimitrova):
What I noticed is that the number of failures is different between 30 and 40 so
they are flaky tests. The issue is only with JDK11 but we didn't change the
image, introducing newer JDK or the jolokia jar that the DTest repo comes with.
I started digging further and I noticed you probably give rerun to the
workflow? Is this correct?
Could it be anything else get cached?
I did another test now - pushed on my end a branch with your ccm repo and I ran
into different problem:
This was trying on an 11 build to run the tests with 8 -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2312/workflows/f7c3bf3f-b3f0-4ab0-82c8-408866dd363c/jobs/18973
This is your commit to your branches on latest trunk.
Then on the same branch with trunk and the current ccm without your branch I
didn't notice that problem:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2313/workflows/0df1adfb-bf74-4477-86d1-bb4830d8d697/jobs/18976
(I cancelled both builds but if you scroll through the steps)
Can you try to trigger your branch by pushing empty commit? I think what you
see is probably cached ccm maybe?
> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
> Key: CASSANDRA-18106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.x
>
>
> As part of CASSANDRA-16895 initial POC an initial version of CCM patch was
> created. This needs to be revisited and reviewed
> Recently we closed CASSANDRA-18039 which brought questions, probably we need
> to revise how we detect JDK versions in CCM and whether it is correct. To the
> best of my knowledge there are certain tests in the repo around that and they
> pass so my guess is we need to revise just the strategy and maybe document it
> explicitly or consider if we want any changes to be applied. Also, we need to
> be careful with breaking changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
