[
https://issues.apache.org/jira/browse/CASSANDRA-16851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416227#comment-17416227
]
Ekaterina Dimitrova edited comment on CASSANDRA-16851 at 9/16/21, 4:35 PM:
---------------------------------------------------------------------------
I didn't see any related issues based on the CI runs.
[~tatu-at-datastax] as our CI is still new to you and I know it can be
overwhelming sometimes, I made the CI results analysis for you as an example.
It is based on [Jenkins post-commit builds
history|https://jenkins-cm4.apache.org/] and already opened tickets for tests
issues - [this Jira
filter|https://issues.apache.org/jira/issues/?filter=12350869], linked by Josh
in the latest [project
updates|https://lists.apache.org/thread.html/r681bcfcfa938569ae7fb86c0c309ee7d84558f1cc07eb2c1a30468c7%40%3Cdev.cassandra.apache.org%3E]
on the mailing list.
*I think we need to open ticket for:*
[org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader[version=5/v5|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/junit/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_5_v5_/]]
which failed in trunk as it is flaky according to Jenkins even without this
patch and it is not related.
[org.apache.cassandra.distributed.test.ClientTombstoneWarningTest.failThresholdSinglePartition|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/org.apache.cassandra.distributed.test/ClientTombstoneWarningTest/failThresholdSinglePartition_2/]
is also consistently failing in trunk and there is no ticket, the failure is
unrelated to this patch.
[org.apache.cassandra.distributed.test.OptimiseStreamsRepairTest.randomTest|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1120/testReport/junit/org.apache.cassandra.distributed.test/OptimiseStreamsRepairTest/randomTest/]
- failed in 4.0. Seems legit issue and we need ticket. From a quick look at
the log I think it will turn test issue as there are overlapping repairs
probably...timing problem. I've seen this before with other tests.
But...again....to be checked, I am speculating based on a very quick look in
Jenkins log excerpt.
[org.apache.cassandra.cql3.ViewTest.testTruncateWhileBuilding|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1119/testReport/junit/org.apache.cassandra.cql3/ViewTest/testTruncateWhileBuilding/]
- failing in 3.11, unrelated; needs a ticket
[org.apache.cassandra.concurrent.LongSharedExecutorPoolTest.testPromptnessOfExecution|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1119/testReport/junit/org.apache.cassandra.concurrent/LongSharedExecutorPoolTest/testPromptnessOfExecution/]
- failing in 3.11, unrelated; needs a ticket
*No ticket needed for:*
[org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest
|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/junit/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/]
- unrelated timeout I think?
dtest-novnode.materialized_views_test.TestMaterializedViews.test_view_metadata_cleanup
- CASSANDRA-16954
offline_tools_test.py::TestOfflineTools::test_sstableverify fails on 3.11 -
CASSANDRA-16948
cqlsh.python2 - I am not sure that those we plan to fix; the failures provides
contradictive Info.
The upgrade tests in 3.11 fail with timeouts or teardown issues -
CASSANDRA-16954
org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate -
CASSANDRA-16681
was (Author: e.dimitrova):
I didn't see any related issues based on the CI runs.
[~tatu-at-datastax] as our CI is still new to you and I know it can be
overwhelming sometimes, I made the CI results analysis for you as an example.
It is based on [Jenkins post-commit builds
history|https://jenkins-cm4.apache.org/] and already opened tickets for tests
issues - [this Jira
filter|https://issues.apache.org/jira/issues/?filter=12350869], linked by Josh
in the latest [project
updates|https://lists.apache.org/thread.html/r681bcfcfa938569ae7fb86c0c309ee7d84558f1cc07eb2c1a30468c7%40%3Cdev.cassandra.apache.org%3E]
on the mailing list.
*I think we need to open ticket for:*
[org.apache.cassandra.distributed.test.UnableToParseClientMessageTest.badHeader[version=5/v5|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/junit/org.apache.cassandra.distributed.test/UnableToParseClientMessageTest/badHeader_version_5_v5_/]]
which failed in trunk as it is flaky according to Jenkins even without this
patch and it is not related.
[org.apache.cassandra.distributed.test.ClientTombstoneWarningTest.failThresholdSinglePartition|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/org.apache.cassandra.distributed.test/ClientTombstoneWarningTest/failThresholdSinglePartition_2/]
is also consistently failing in trunk and there is no ticket, the failure is
unrelated to this patch.
[org.apache.cassandra.distributed.test.OptimiseStreamsRepairTest.randomTest|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1120/testReport/junit/org.apache.cassandra.distributed.test/OptimiseStreamsRepairTest/randomTest/]
- failed on 4.0; I see it flaky in Jenkins and unrelated to this patch; there
is no ticket opened yet.
[org.apache.cassandra.distributed.test.OptimiseStreamsRepairTest.randomTest|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1120/testReport/junit/org.apache.cassandra.distributed.test/OptimiseStreamsRepairTest/randomTest/]
- failed in 4.0. Seems legit issue and we need ticket. From a quick look at
the log I think it will turn test issue as there are overlapping repairs
probably...timing problem. I've seen this before with other tests.
But...again....to be checked, I am speculating based on a very quick look in
Jenkins log excerpt.
[org.apache.cassandra.cql3.ViewTest.testTruncateWhileBuilding|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1119/testReport/junit/org.apache.cassandra.cql3/ViewTest/testTruncateWhileBuilding/]
- failing in 3.11, unrelated; needs a ticket
[org.apache.cassandra.concurrent.LongSharedExecutorPoolTest.testPromptnessOfExecution|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1119/testReport/junit/org.apache.cassandra.concurrent/LongSharedExecutorPoolTest/testPromptnessOfExecution/]
- failing in 3.11, unrelated; needs a ticket
*No ticket needed for:*
[org.apache.cassandra.distributed.upgrade.CompactStorageUpgradeTest.compactStorageUpgradeTest
|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1121/testReport/junit/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageUpgradeTest/]
- unrelated timeout I think?
dtest-novnode.materialized_views_test.TestMaterializedViews.test_view_metadata_cleanup
- CASSANDRA-16954
offline_tools_test.py::TestOfflineTools::test_sstableverify fails on 3.11 -
CASSANDRA-16948
cqlsh.python2 - I am not sure that those we plan to fix; the failures provides
contradictive Info.
The upgrade tests in 3.11 fail with timeouts or teardown issues -
CASSANDRA-16954
org.apache.cassandra.utils.memory.LongBufferPoolTest.testAllocate -
CASSANDRA-16681
> Update from Jackson 2.9 to 2.12
> -------------------------------
>
> Key: CASSANDRA-16851
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16851
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Tatu Saloranta
> Assignee: Tatu Saloranta
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Given that Jackson 2.9 support has ended, it would be good to move at least
> to the next minor version (2.10, patch 2.10.5) or later – latest stable being
> 2.12.4.
> I can test to see if anything breaks, but looking at existing Jackson usage
> there shouldn't be many issues.
> Assuming upgrade is acceptable there's the question of which branches to
> apply it to; I will first test it against 4.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
