[
https://issues.apache.org/jira/browse/CASSANDRA-19650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849257#comment-17849257
]
Michael Semb Wever edited comment on CASSANDRA-19650 at 5/24/24 12:46 PM:
--------------------------------------------------------------------------
CI using both patches (which fixes all^ problems)
- https://github.com/riptano/ccm/pull/769
- https://github.com/riptano/ccm/pull/770
5.0 all dtests (doesn't cover any of the breakages)
- [^CASSANDRA-19650_50_84_ci_summary.html] and
[^CASSANDRA-19650_50_84_ci_summary.htmlresults_details.tar.xz]
Trunk all dtests (doesn't cover any of the breakages)
- [^CASSANDRA-19650_trunk_85_ci_summary.html] and
[^CASSANDRA-19650_trunk_85_results_details.tar.xz]
4.1 dtest (doesn't cover any of the breakages)
- https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-dtest/5/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-dtest/5/
4.1 dtest-upgrade (doesn't cover any of the breakages)
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-dtest-upgrade/5/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-dtest-upgrade/5/
[~aweisberg] confirmed on the PR
[here|https://github.com/riptano/ccm/pull/770#pullrequestreview-2074344248] his
breakages are fixed.
4.1 cqlsh-test (does cover a breakage)
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-cqlsh-tests/4/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-cqlsh-tests/4/
4.0 cqlsh-test
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-cqlsh-tests/5/
Everything looks good!
was (Author: michaelsembwever):
CI using both patches (which fixes all^ problems)
- https://github.com/riptano/ccm/pull/769
- https://github.com/riptano/ccm/pull/770
5.0 all dtests (doesn't cover any of the breakages)
- [^CASSANDRA-19650_50_84_ci_summary.html] and
[^CASSANDRA-19650_50_84_ci_summary.htmlresults_details.tar.xz]
Trunk all dtests (doesn't cover any of the breakages)
-
4.1 dtest (doesn't cover any of the breakages)
- https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-dtest/5/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-dtest/5/
4.1 dtest-upgrade (doesn't cover any of the breakages)
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-dtest-upgrade/5/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-dtest-upgrade/5/
[~aweisberg] confirmed on the PR
[here|https://github.com/riptano/ccm/pull/770#pullrequestreview-2074344248] his
breakages are fixed.
4.1 cqlsh-test (does cover a breakage)
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-cqlsh-tests/4/
-
https://nightlies.apache.org/cassandra/devbranch/Cassandra-devbranch-before-5-cqlsh-tests/4/
4.0 cqlsh-test
-
https://ci-cassandra.apache.org/job/Cassandra-devbranch-before-5-cqlsh-tests/5/
Everything looks good!
> CCM wrongly interprets CASSANDRA_USE_JDK11 for Cassandra 4.x
> ------------------------------------------------------------
>
> Key: CASSANDRA-19650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19650
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Test/dtest/python
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x
>
> Attachments: CASSANDRA-19650_50_84_ci_summary.html,
> CASSANDRA-19650_50_84_ci_summary.htmlresults_details.tar.xz,
> CASSANDRA-19650_trunk_85_ci_summary.html,
> CASSANDRA-19650_trunk_85_results_details.tar.xz
>
>
> CCM interprets {{CASSANDRA_USE_JDK11}} only by its existence in the
> environment rather than by its actual value (true/false).
> I can see two solutions:
> - make it interpret {{CASSANDRA_USE_JDK11}} properly
> - do not take into account {{CASSANDRA_USE_JDK11}} in the current env and set
> it or unset it automatically when starting a node basing on which Java
> version was selected
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
