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

Michael Semb Wever commented on CASSANDRA-19650:
------------------------------------------------

All CI, all branches before 5, is currently broken because of CASSANDRA-19636

Specifically the cqlsh ({{`pylib/cassandra-cqlsh-tests.sh`}}) tests.
{noformat}

18:29:42 + ccm create test -n 1 --install-dir=/home/cassandra/cassandra
18:29:43 Current cluster is now: test
18:29:43 16:29:43,74 ccm DEBUG using balanced tokens for non-vnode cluster
18:29:43 + ccm updateconf 'user_defined_functions_enabled: true'
18:29:44 + ccm updateconf 'scripted_user_defined_functions_enabled: true'
18:29:44 ++ ccm node1 versionfrombuild
18:29:44 + version_from_build=4.1.6
18:29:44 ++ python -c 'from distutils.version import LooseVersion
18:29:44 print ("postcdc" if LooseVersion("4.1.6") >= "3.8" else "precdc")
18:29:44 '
18:29:45 <string>:2: DeprecationWarning: distutils Version classes are 
deprecated. Use packaging.version instead.
18:29:45 + export pre_or_post_cdc=postcdc
18:29:45 + pre_or_post_cdc=postcdc
18:29:45 + case "${pre_or_post_cdc}" in
18:29:45 + ccm updateconf 'cdc_enabled: true'
18:29:45 + ccm start --wait-for-binary-proto
18:29:46 16:29:46,124 ccm INFO Supported Java versions for Cassandra 
distribution in '/home/cassandra/cassandra': None
18:29:46 16:29:46,186 ccm WARNING node1: The current Java 8 is not supported by 
Cassandra 4.1.6 (supported versions: [11]).
18:29:46 Traceback (most recent call last):
18:29:46   File "/home/cassandra/cassandra/venv/bin/ccm", line 7, in <module>
18:29:46     exec(compile(f.read(), __file__, 'exec'))
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccm", line 112, in 
<module>
18:29:46     cmd.run()
18:29:46   File 
"/home/cassandra/cassandra/venv/src/ccm/ccmlib/cmds/cluster_cmds.py", line 513, 
in run
18:29:46     if self.cluster.start(no_wait=self.options.no_wait,
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccmlib/cluster.py", 
line 526, in start
18:29:46     p = node.start(update_pid=False, jvm_args=jvm_args, 
jvm_version=jvm_version,
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccmlib/node.py", line 
820, in start
18:29:46     env = self.get_env()
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccmlib/node.py", line 
240, in get_env
18:29:46     env = common.update_java_version(jvm_version=None,
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccmlib/common.py", line 
960, in update_java_version
18:29:46     return _update_java_version(current_java_version, 
current_java_home_version,
18:29:46   File "/home/cassandra/cassandra/venv/src/ccm/ccmlib/common.py", line 
1031, in _update_java_version
18:29:46     raise RuntimeError('{}: Cannot find any Java distribution for the 
current invocation. Available Java distributions: {}, required Java 
distributions: {}'
18:29:46 RuntimeError: node1: Cannot find any Java distribution for the current 
invocation. Available Java distributions: {8: 'JAVA_HOME'}, required Java 
distributions: [11]
{noformat}

Ref:
 - https://ci-cassandra.apache.org/job/Cassandra-4.1-cqlsh-tests/435/
 - 
https://nightlies.apache.org/cassandra/cassandra-4.1/Cassandra-4.1-cqlsh-tests/435/Cassandra-4.1-cqlsh-tests/cython=no,jdk=jdk_1.8_latest,label=cassandra/


This is because it was expecting {{`CASSANDRA_USE_JDK11=false`}} to work.  It 
never did, but before 19636 was being ignored.
Ref: 
https://github.com/apache/cassandra/blob/cassandra-4.1/pylib/cassandra-cqlsh-tests.sh#L47
 



> 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: NA
>
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to