av9ash/GitBugs huggingface dataset:
Bug: Package tools/bin scripts as executable
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 30/Sep/20 09:05
Resolved: 21/Oct/20 12:40

The tools/bin scripts aren't packaged as executable in the source distributions, though in the repository the scripts have the right bits.

This causes, on 3.11.8 for example, the tests in org.apache.cassandra.cql3.EmptyValuesTest to fail:
{{java.io.IOException: Cannot run program "tools/bin/sstabledump": error=13, Permission denied}}

{{[junit-timeout] junit.framework.AssertionFailedError: java.io.IOException}}
{{[junit-timeout]         at org.apache.cassandra.cql3.EmptyValuesTest.verify(EmptyValuesTest.java:85)}}
{{[junit-timeout]         at org.apache.cassandra.cql3.EmptyValuesTest.verifyJsonInsert(EmptyValuesTest.java:112)}}

See attached patch of build.xml for the trunk and cassandra-3.11 branches.
Bug: Throw FSWriteError upon write failures in order to apply DiskFailurePolicy
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 07/Jul/20 22:13
Resolved: 03/Aug/20 15:37

Active handling of FSError in AbstractLocalAwareExecutorService was introduced in CASSANDRA-14993. 
 
However, in the current code base, there are places that catch the IOException but not wrap it with FSError, hence not triggering the DiskFailurePolicy. Especially when the bad disk no longer permits write operations, it could leads to the mutation stage backup. Therefore I propose to fix the IOException handling in those cases. 
 
From the code inspection, those 6 places are current not re-throwing an IOException with FSWriteError.
 # org.apache.cassandra.triggers.CustomClassLoader#addClassPath throws IOError. Invoked in TriggerExecutor's constructor
 # org.apache.cassandra.io.util.FileUtils#renameWithConfirm throws RuntimeException
 # org.apache.cassandra.io.util.FileUtils#truncate throws RuntimeException
 # org.apache.cassandra.io.util.FileUtils#write throws RuntimeException
 # org.apache.cassandra.db.compaction.LeveledManifest#sendBackToL0 throws RuntimeException. Invokes rewriteSSTableMetadata
 # org.apache.cassandra.io.sstable.SSTableHeaderFix#writeNewMetadata throws RuntimeException. Invokes rewriteSSTableMetadata
Bug: Repair tests flakiness
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 27/Jul/20 14:22
Resolved: 06/Oct/20 17:13

Repair tests come up in test failure reports every now and then. I have tried to repro the [latest|https://ci-cassandra.apache.org/job/Cassandra-trunk/241/testReport/junit/dtest-novnode.repair_tests.repair_test/TestRepair/test_simple_sequential_repair/] locally 100 times with no luck.
_dtest-novnode.repair_tests.repair_test/TestRepair/test_simple_sequential_repair_

Still from experience from fixing other flaky tests I have some intuition where the problems may lie. The proposed fix should add no harm if merged. We can reopen the ticket if repair tests keep failing.
Bug: JMX output inconsistencies from CASSANDRA-7544 storage-port-configurable-per-node
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 11/Jul/20 00:03
Resolved: 26/Aug/20 21:03

CASSANDRA-7544 introduced changes to allow the storage port number to be configured per-node. As part of that work it introduces new MBeans for MessagingService, FailureDetector providing new 'WithPort' versions that include the new port information, however there are some mistakes and inconsistencies.
{code:java}
                           3.11.6                trunk                  trunk w/Port          Notes
  
 AllEndpointStates        /127.0.0.1\n...       /127.0.0.3\n...        127.0.0.3:7000\n        (trunk /w port different)
 SimpleStates             /127.0.0.2=UP         /127.0.0.2=UP          127.0.0.3:7000=UP       (trunk /w port different)
 LargeMessagePendingTasks /127.0.0.1=0          /127.0.0.1=0           127.0.0.3:7000=0        (trunk /w port different)
 TimeoutsPerHost          127.0.0.1=0           /127.0.0.1=0           127.0.0.3:7000=0        3.0/3.11.6 & trunk differ.
 BackPressurePerHost      127.0.0.1=Infinity    /127.0.0.2=Infinity    /127.0.0.2=Infinity     3.11 & trunk differ, missing port number for BackPressurePerHostWithPort
 SchemaVersions          {...=[127.0.0.1,...]} {...=[127.0.0.1,...]}  {...=[127.0.0.1:7000,...]
  
 TokenToEndpointMap      {-92...8=127.0.0.1,   -92...8=127.0.0.1      -92..8=127.0.0.1:7000
 HostIdMap               127.0.0.1=1ee..6f0af  127.0.0.1=e06...7e     MISSING                  Deprecated for EndpointToHostId
 EndpointToHostId        127.0.0.1=1ee..6f0a   127.0.0.1=e06...7e     127.0.0.1:7000=e0..7e
 HostIdToEndpoint        1ee..6f0a=127.0.0.1   e06..7e=127.0.0.1      e06..7e=127.0.0.1:7000
 LoadMap                 127.0.0.1=185.01 KiB  127.0.0.1:7000=106.08 KiB  127.0.0.1=106.08 Ki  LoadMap and LoadMapWithPort are flipped.
 LiveNodes               127.0.0.1             127.0.0.1              127.0.0.1:7000
 Ownership               /127.0.0.1=0.333333   /127.0.0.1=0.333333    127.0.0.1:7000=0.333333
 Scores                  /127.0.0.1=0.0        /127.0.0.1=0.0         127.0.0.1:7000=0.0
  {code}
 
 Proposed changes
  
 1) AllEndpointStats, SimpleStates, Connection message tracking, TimeoutsPerHost - include the host/ip:port in the WithPort version
2) Add port number to BackPressurePerHostWithPort
3) Correct LoadMap to omit port / LoadMapWithPort to include port
4) Ownership - update with port to host/ip:port version
5) Scores - update with port to host/ip:port version
  
  
 Additionally while dumping out all of the JMX info with `sjk mxdump`
  
6) DynamicEndpointSnitch.getScoresWithPort now returns an InetAddressAndPort which should just be a String
7) ClientMetrics.clientsByProtocolVersion returns a Guava Immutable map
8) StorageService.getIdealConsistencyLevel fails if none set (as we try and call ConsistencyLevel.toString on a null pointer).
Bug: When jvm dtest apis differ Circle CI's dtest_jars_build can fail to detect this and will use the jars from the older version
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 31/Jul/20 00:36
Resolved: 03/Aug/20 22:20

https://app.circleci.com/pipelines/github/dcapwell/cassandra/389/workflows/ea7776ac-5be0-4cb4-ab4c-61f524397c07/jobs/2019

{code}
build-test:
    [javac] Compiling 510 source files to /home/cassandra/cassandra/build/test/classes
    [javac] warning: Supported source version 'RELEASE_6' from annotation processor 'org.openjdk.jmh.generators.BenchmarkProcessor' less than -source '1.8'
    [javac] /home/cassandra/cassandra/test/distributed/org/apache/cassandra/distributed/impl/RowUtil.java:49: error: no suitable constructor found for SimpleQueryResult(String[],Object[][],warnings =[...]nings)
    [javac]             return new SimpleQueryResult(names, results, warnings == null ? Collections.emptyList() : warnings);
    [javac]                    ^
    [javac]     constructor SimpleQueryResult.SimpleQueryResult(String[],Object[][]) is not applicable
    [javac]       (actual and formal argument lists differ in length)
    [javac]     constructor SimpleQueryResult.SimpleQueryResult(String[],Object[][],Predicate<Row>,int) is not applicable
    [javac]       (actual and formal argument lists differ in length)
    [javac] /home/cassandra/cassandra/test/distributed/org/apache/cassandra/distributed/test/ReplicaFilteringProtectionTest.java:212: error: cannot find symbol
    [javac]         List<String> futureWarnings = futureResult.warnings();
    [javac]                                                   ^
    [javac]   symbol:   method warnings()
    [javac]   location: variable futureResult of type SimpleQueryResult
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 2 errors
    [javac] 1 warning

BUILD FAILED
/home/cassandra/cassandra/build.xml:1176: Compile failed; see the compiler error output for details.
{code}

cassandra-3.0 compiled against the dtest jar provided by cassandra-2.2, so failed.
Bug: in-jvm dtests should validate Instance#serializeMessage serializeSize matches bytes written
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 08/Sep/20 19:03
Resolved: 09/Sep/20 02:08

In 3.0 sizeOf is an optimization but in 4.0 its used for message header and as such must be correct; this check is not done when mock messaging is used so may ignore mixed-mode issues.
Bug: Blog post on Cassandra Usage Report 2020
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Sep/20 02:13
Resolved: 17/Sep/20 19:11

Blog post on the 2020 Cassandra Usage Report.

ML: [https://lists.apache.org/thread.html/r8a91b1d63079739c8dfbdab1833c66d58326de91a659afa3fb2a41a7%40%3Cdev.cassandra.apache.org%3E] 

PR: [https://github.com/apache/cassandra-website/pull/21]
Bug: Add test which validates that Message serializedSize(version) == serialize(out, version).length
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 20/Aug/20 21:37
Resolved: 26/Aug/20 22:27

In 4.0 we require serializedSize(version) == serialize(out, version).length for correctness in post40 message format as we write it into the message header.  Given that this is a strong requirement for correct deserialization of the message, we should have tests which help enforce this property.
Bug: MessageSerializationPropertyTest fails with bytes should not be empty for type org.apache.cassandra.db.marshal.BytesType
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 31/Aug/20 16:54
Resolved: 31/Aug/20 19:35

{code}
Cause was :-
java.lang.AssertionError: bytes should not be empty for type org.apache.cassandra.db.marshal.BytesType
	at org.apache.cassandra.db.marshal.AbstractType.writtenLength(AbstractType.java:423)
	at org.apache.cassandra.db.SinglePartitionReadCommand.selectionSerializedSize(SinglePartitionReadCommand.java:1043)
	at org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:1038)
	at org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:909)
	at org.apache.cassandra.net.Message$Serializer.payloadSize(Message.java:1289)
	at org.apache.cassandra.net.Message.payloadSize(Message.java:1333)
	at org.apache.cassandra.net.Message$Serializer.serializePre40(Message.java:917)
	at org.apache.cassandra.net.Message$Serializer.serialize(Message.java:620)
	at org.apache.cassandra.net.MessageSerializationPropertyTest.lambda$serializeSizeProperty$0(MessageSerializationPropertyTest.java:73)

Seed was 35361441975355
{code}

This is caused by the fact the generators allow empty types.
Bug: org.apache.cassandra.net.ConnectionTest testMessagePurging
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 17/Jul/20 23:34
Resolved: 07/Oct/20 11:02

Build: https://ci-cassandra.apache.org/job/Cassandra-trunk-test/196/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessagePurging/
Build: https://ci-cassandra.apache.org/job/Cassandra-trunk-test/194/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessagePurging/
java.util.concurrent.TimeoutException
	at org.apache.cassandra.net.AsyncPromise.get(AsyncPromise.java:258)
	at org.apache.cassandra.net.FutureDelegate.get(FutureDelegate.java:143)
	at org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:268)
	at org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:236)
	at org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:679)
Bug: how_to_commit.rst missing dash in git commands and added recommendation to compile before commit
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 25/Jul/20 21:04
Resolved: 27/Jul/20 18:40

There are two typos in how_to_commit.rst: -amend -> --amend and -atomic -> --atomic.

Also, the docs don't recommend building before committing, would be best to encourage this.
Bug: Fix flaky test StreamingInboundHandlerTest channelRead_Normal
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 21/Jul/20 19:28
Resolved: 16/Sep/20 21:35

channelRead_Normal - org.apache.cassandra.streaming.async.StreamingInboundHandlerTest

{code}
junit.framework.AssertionFailedError: expected:<8> but was:<0>
	at org.apache.cassandra.streaming.async.StreamingInboundHandlerTest.channelRead_Normal(StreamingInboundHandlerTest.java:98)
{code}

Failed build: https://app.circleci.com/pipelines/github/dcapwell/cassandra/298/workflows/e3296f33-2289-401c-8fc8-a7f786e3692a/jobs/1445
Bug: 15583 - Add UX tests to intree LHF tooling
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 28/Jul/20 09:01
Resolved: 30/Sep/20 22:04

As per CASSANDRA-15583 many in tree tools lack proper UX tooling: mandatory params are indeed mandatory, 'help' produces an actual help, return codes etc

This ticket is an attempt to add it to those tools that classify as LHF. Other tools such as nodetool, with many sub-commands, deserve a separate ticket of their own
Bug: NPE in StreamingMessage type lookup
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 16/Sep/20 21:29
Resolved: 16/Sep/20 21:34

Found while investigating https://issues.apache.org/jira/browse/CASSANDRA-15965

{noformat}
java.lang.NullPointerException: null
	at org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:51)
	at org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)
{noformat}

There is a null in the zero.index of the type map. We can clean this up, handle invalid ids in a uniform manner, and add a test.
Bug: NPE when sending REQUEST_RSP from 3.0 to 4.0 in in-jvm dtests
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 15/Jul/20 07:22
Resolved: 18/Aug/20 16:48

There is a communication problem when testing upgrades using in-JVM dtest between Cassandra 3 and 4. 

In a method {{registerInboundFilter}} of {{Instance}}, we get a message which was just received and we prepare it for filtering as part of which, we serialize the payload again. This is fine when dealing with incoming Cassandra 4 message, because we can serialize it. However when we get the Cassandra 3 message, which uses a different protocol, and we get something like {{REQUEST_RSP}}, we can surely deserialize it through some special deserialization path, but we cannot serialize the payload for it as there is no serializer defined for {{REQUEST_RSP}} - no wonder, why would Cassandra 4.0 need to be able to serialize Cassandra 3.0 payloads?

{code}
java.lang.NullPointerException: null
	at org.apache.cassandra.net.Message$Serializer.serializePost40(Message.java:760)
	at org.apache.cassandra.net.Message$Serializer.serialize(Message.java:618)
	at org.apache.cassandra.distributed.impl.Instance.serializeMessage(Instance.java:267)
	at org.apache.cassandra.distributed.impl.Instance.lambda$registerInboundFilter$4(Instance.java:234)
	at org.apache.cassandra.net.InboundSink$Filtered.accept(InboundSink.java:62)
	at org.apache.cassandra.net.InboundSink$Filtered.accept(InboundSink.java:49)
	at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:93)
	at org.apache.cassandra.distributed.impl.Instance.lambda$null$6(Instance.java:305)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:165)
	at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:137)
	at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)
{code}
Bug: dtest: Fix redundant TTL overflow policy tests
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 24/Sep/20 21:29
Resolved: 25/Sep/20 16:03

While looking into CASSANDRA-15996 I came across what I think is a copy/paste mistake resulting in redundant tests, and not running the other variant. 

Spinning out here to fix independently of the flaky test.
Bug: InvalidQuery when datetime string format is not zero padded
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 03/Sep/20 16:47
Resolved: 15/Sep/20 15:45

With CASSANDRA-15976, Cassandra no longer accepts certain datetime string formats that it used to accept before:

{code:java}
Unable to parse a date/time from '2020-09-03 9:00:00+0000'
{code}

In this example, {{2020-09-03 9:00:00+0000}} is not accepted in 4.0-beta2 but it is accepted in previous versions (I tested this with 4.0-beta1 and 3.11.4). If I add a zero so that it becomes {{2020-09-03 09:00:00+0000}} then it is accepted in all of the 3 mentioned versions (note the zero padded time part - {{9:00:00}} vs {{09:00:00}})
Bug: cqlsh tests broken in Python 3.7+
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Aug/20 18:02
Resolved: 05/Aug/20 18:48

{code:java}
// cassandra/pylib/cqlshlib/test/run_cqlsh.py", line 221, in read_until
    if not isinstance(until, re._pattern_type):
AttributeError: module 're' has no attribute '_pattern_type'
{code}
An internal module attribute was changed/removed from Python 3.7 on.

[https://github.com/python/cpython/pull/1646/files#diff-daea55f2fca784d9a64ca8f190403904R267-L272]

This breakage did not manifest in CI because the test use the Jenkins host system Python, which is 3.6.

I have a trivial patch I'll add shortly.
Bug: Startup fails with NoClassDefFoundError after CASSANDRA-15884
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 07/Jul/20 23:03
Resolved: 08/Jul/20 15:07

CASSANDRA-15884 added logic to detect if the native lib of lz4 was properly loaded and to log a warning if this was not the case, it seems that the catch for this didn’t handle the class loading issue that also happens in this case.

{code}
ERROR [main] 2020-07-07 22:49:32,560 CassandraDaemon.java:800 - Exception encountered during startup
java.lang.NoClassDefFoundError: Could not initialize class net.jpountz.lz4.LZ4JNI
       at net.jpountz.lz4.LZ4JNICompressor.compress(LZ4JNICompressor.java:36)
       at net.jpountz.lz4.LZ4Factory.<init>(LZ4Factory.java:207)
       at net.jpountz.lz4.LZ4Factory.instance(LZ4Factory.java:51)
       at net.jpountz.lz4.LZ4Factory.nativeInstance(LZ4Factory.java:91)
       at org.apache.cassandra.service.StartupChecks.lambda$static$0(StartupChecks.java:149)
       at org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:127)
       at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:211)
       at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:661)
       at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:778)
{code}

After patching, the following is the behavior

WARN  [main] 2020-07-07 22:50:45,018 StartupChecks.java:153 - lz4-java was unable to load native libraries; this will lower the performance of lz4 (network/sstables/etc.): Could not initialize class net.jpountz.lz4.LZ4JNI
Bug: Improve machinery for testing consistency in presence of range movements
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 10/Jul/20 14:29
Resolved: 22/Oct/20 08:09

Currently, we can test range movements only by adding and bootstrapping a new node. This is both inefficient and insufficient for large-scale tests. We need a possibility to dynamically change ring ownership over the lifetime of cluster, with a flexibility to changing gossip status of the node from perspective of other participants, adding and removing nodes from other nodes' views on demand.
Bug: Create better third-party page
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 13/Jul/20 23:04
Resolved: 20/Jul/20 22:34

Create a better third-party page based on dev mailing list conversation.

https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E
Bug: Verify expected SSTable components are present at startup
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 14/Jul/20 17:36
Resolved: 20/Jul/20 19:31

When Cassandra batch opens all sstables at startup, it should check that all components listed in the TOC.txt are available. Compression is optional, so there may not be a Compression.db component for all sstables, but if there should be and it's missing we continue to load the sstable. The sstable is unreadable without the compression metadata though, but we won't know this until it's touched by a query or compaction.

To reliably use TOC.txt for verification, it needs CASSANDRA-10709
Bug: Invalid version value: 4.0~alpha4
Status: Resolved
Priority: Normal
Resolution: Duplicate
Created: 16/Jul/20 07:26
Resolved: 16/Jul/20 09:26

hello : 

i was started cassandra  4.0 in Centos 7. When i started everything is fine, but when i stop then start again i get an error like this.


ERROR [main] 2020-07-16 14:25:11,330 CassandraDaemon.java:789 - Exception encountered during startup
java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
        at org.apache.cassandra.utils.CassandraVersion.<init>(CassandraVersion.java:64)
        at org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
        at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
        at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
        at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
Bug: TestBootstrap::test_node_cannot_join_as_hibernating_node_without_replace_address failing on trunk
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 05/Aug/20 21:20
Resolved: 11/Aug/20 14:41

{{TestBootstrap::test_node_cannot_join_as_hibernating_node_without_replace_address}} seems to think that the new replacement node is running when it shouldn’t be. We’ve got two confirmed failures, one on trunk and one on a recent trunk-based patch:

https://ci-cassandra.apache.org/job/Cassandra-trunk/259/testReport/dtest-novnode.bootstrap_test/TestBootstrap/test_node_cannot_join_as_hibernating_node_without_replace_address/

https://app.circleci.com/pipelines/github/adelapena/cassandra/79/workflows/1fa1cbcf-820d-438f-97bd-91e20a50baba/jobs/604
Bug: sstablemetadata unit test, docs and params parsing hardening
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/20 09:01
Resolved: 06/Oct/20 20:20

During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}. Also docs are missing some options and args parsing is brittle.
Bug: sstablesplit unit test hardening
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 04/Aug/20 08:55
Resolved: 09/Oct/20 14:21

 
During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage for this tool is minimal. There is a unit test to enhance upon under {{test/unit/org/apache/cassandra/tools}}.
Bug: ASF CI unit tests on JDK11
Status: Resolved
Priority: Normal
Resolution: Fixed
Created: 14/Jul/20 14:05
Resolved: 20/Oct/20 16:09

ASF CI tests today only run on JDK1.8

On the Jenkins cluster JDKs from 1.4 through to 15 are available. See screenshot for naming specifics, attached in  CASSANDRA-15809

 

This ticket is to add JDK11 test targets on Cassandra-trunk and Cassandra-devbranch, for parity to CircleCI's workflows.

 

The JDK is specified in the groovy DSL:
 [https://github.com/apache/cassandra-builds/blob/master/jenkins-dsl/cassandra_job_dsl_seed.groovy#L11] 

 This is a continuation from CASSANDRA-15809