[
https://issues.apache.org/jira/browse/CASSANDRA-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534437#comment-17534437
]
David Capwell commented on CASSANDRA-17549:
-------------------------------------------
Speaking in Slack [~benedict] pointed out that Futures should log before due to
us extracting the error from the FutureTask, but this only happens if the
FutureTask was success after execution...
We also switched IR to throw SomeRepairFailedException rather than have flatMap
return a failed future, so that change is what actually triggered the new
logging... switching back to flatMap with failed future avoids the logging...
will create a new JIRA for this issue
> jvm-dtest unhandled exceptions failing the test no longer work
> --------------------------------------------------------------
>
> Key: CASSANDRA-17549
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17549
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1
>
>
> Seems that ([CASSANDRA-16925] CEP-10 Phase 1: Mockable Task Execution)
> refactored and avoided using AbstractCluster.uncaughtException, this means
> that the logic to detect unexpected exceptions to fail tests no longer works.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
