[
https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625868#comment-17625868
]
Ekaterina Dimitrova edited comment on CASSANDRA-17987 at 10/28/22 7:39 PM:
---------------------------------------------------------------------------
{quote}diffs of diffs
{quote}
:D my favorite
3.0 - do we need also to recreate again the patches? I didn't test but I
suspect we will be getting again those warnings, no?
CI-wise - 4.0 caught a flaky test, 4.1 needs another push of the unit tests as
it seems you hit env issue. I hit the same yesterday.I am sure simple rerun
will fix it.
I tried to verify also that nothing shifted with MIDRES and HIGHRES with the
patching on all branches.
Overall I am +1 here, thank you for tackling this
was (Author: e.dimitrova):
{quote}diffs of diffs
{quote}
:D my favorite
3.0 - do we need also to recreate again the patches? I didn't test but I
suspect we will be getting again those warnings, no?
CI-wise - 4.0 caught a flaky test, 4.1 needs another push of the unit tests as
it seems you hit env issue. I hit the same yesterday.I am sure simple rerun
will fix it.
I tried to verify also that nothing shifted with MIDRES and HIGHRES with the
patching.
Overall I am +1 here, thank you for tackling this
> CircleCI: Add jobs for running specialized unit tests with Java 11
> ------------------------------------------------------------------
>
> Key: CASSANDRA-17987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17987
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
>
> CircleCI has a set of jobs for running specialiazed unit tests that are only
> run with Java 8:
> * utests_compression
> * utests_system_keyspace_directory
> * utests_trie
> * utests_stress
> * utests_long
> * utests_fqltool
> It should probably be possible to run these tests with Java 11 tool.
> Rather than creating a ticket for every job, it's probably easier to use a
> single ticket for all of them. This should give us an overall vision for
> deciding job names, approval steps, etc. Also, the required config changes
> should be quite minimal and doing all of them at once should save us both
> effort and test runs.
--
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
