[
https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771642#comment-17771642
]
Ekaterina Dimitrova commented on CASSANDRA-14667:
-------------------------------------------------
5.0: test_decommission - test failure, timeout; I think it was just because we
fired all possible tests; even CircleCI cannot catch up at times. The test
doesn't fail locally for me.
trunk: LGTM; one of the containers is marked in red, but:
{code:java}
===End Flaky Test Report===
============ 23 passed, 3 skipped, 4 warnings in 3141.13s (0:52:21) ============
Too long with no output (exceeded 15m0s): context deadline exceeded
{code}
I've seen this before in CircleCI, but it has nothing to do with the tests
themselves.
+1
> Upgrade Dropwizard Metrics to 4.x
> ---------------------------------
>
> Key: CASSANDRA-14667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14667
> Project: Cassandra
> Issue Type: Task
> Components: Observability/Metrics
> Reporter: Stig Rohde Døssing
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: signature.asc, signature.asc, signature.asc,
> signature.asc
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for
> Java 9 compatibility. It would be good to upgrade the Metrics library as part
> of the version of Cassandra that adds Java 9 compatibility
> (https://issues.apache.org/jira/browse/CASSANDRA-9608).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
