[
https://issues.apache.org/jira/browse/CASSANDRA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435487#comment-17435487
]
Benedict Elliott Smith commented on CASSANDRA-17050:
----------------------------------------------------
[dtest-api|https://github.com/belliottsmith/cassandra-in-jvm-dtest-api/tree/17050]
It looks like Jenkins CI has its own issues, as I don't think CQLSHLIB tests
have been affected by this or earlier work, and 2.2 has failing python dtests
that are definitely unrelated.
CircleCI is now showing upgrade dtests as clean, and I have the other jvm
dtests for confirmation. However we will need to release a new dtest-api
(preferably to include CASSANDRA-17064) before we merge this.
I wonder if we should aim to reduce the friction for internal dependencies by
using the apache snapshots repository for non-release builds. Not sure if
somebody has a better idea, but today it is more than a little annoying to have
to release the dtest-api before merging any change that uses it. The problem
may become more common as we accumulate more sub-projects.
> 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: Urgent
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
