[
https://issues.apache.org/jira/browse/CASSANDRA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431332#comment-17431332
]
Benedict Elliott Smith commented on CASSANDRA-17050:
----------------------------------------------------
[17050-trunk|https://github.com/belliottsmith/cassandra/tree/17050-trunk]
[17050-4.0|https://github.com/belliottsmith/cassandra/tree/17050-4.0]
[17050-3.11|https://github.com/belliottsmith/cassandra/tree/17050-3.11]
[17050-3.0|https://github.com/belliottsmith/cassandra/tree/17050-3.0]
[17050-2.2|https://github.com/belliottsmith/cassandra/tree/17050-2.2]
The {{trunk}} patch addresses the issue referenced by this ticket, however
another problem also arose due to a bug in the past usage of the dtest-api.
Specifically, all prior versions cast {{IInstanceConfig}} to the concrete
{{InstanceConfig}} inside of {{Instance.loadConfig}} - which is of course
unsafe if this class is modified by the later version (and fundamentally breaks
the encapsulation offered by the dtest-api).
I have therefore had to upgrade all versions to the latest dtest-api, except
for 2.2 which I have cheated by simply grabbing the {{getParams}} method by
reflection.
> Upgrade tests fail with InvocationTargetException
> -------------------------------------------------
>
> Key: CASSANDRA-17050
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17050
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: Benedict Elliott Smith
> Assignee: Benedict Elliott Smith
> Priority: Normal
>
> Upgrade tests are currently failing due to the new dtest-api changes and
> their integration with trunk.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
