[jira] [Comment Edited] (CASSANDRA-17050) Upgrade tests fail with InvocationTargetException
[ https://issues.apache.org/jira/browse/CASSANDRA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436274#comment-17436274 ] Michael Semb Wever edited comment on CASSANDRA-17050 at 10/30/21, 7:26 PM: --- CI - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1257/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1257/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1255/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1255/] (10 more failures, 28 vs 18) - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1254/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1254/] (7 more failures than 3.11, 48 vs 41) - 3.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1253/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1253/] (28 more failures than 3.0, 54 vs 26) - 2.2 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch-jvm-dtest-upgrade/885/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch-jvm-dtest-upgrade/885/] was (Author: michaelsembwever): CI - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1256/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1256/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1255/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1255/] - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1254/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1254/] - 3.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1253/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1253/] - 2.2 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch-jvm-dtest-upgrade/885/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch-jvm-dtest-upgrade/885/] > 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
[jira] [Comment Edited] (CASSANDRA-17050) Upgrade tests fail with InvocationTargetException
[ https://issues.apache.org/jira/browse/CASSANDRA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435661#comment-17435661 ] Michael Semb Wever edited comment on CASSANDRA-17050 at 10/28/21, 9:16 PM: --- bq. 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. Yes. This was discussed a little [here|https://issues.apache.org/jira/browse/CASSANDRA-16649?focusedCommentId=17341901&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17341901] and the comment after it. I'm not confident yet of any other approach but the "throwaway" commits introducing the snapshot repository in patches (which are akin to the circle "throwaway" commits). was (Author: michaelsembwever): bq. 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. Yes. This was discuss a little [here|https://issues.apache.org/jira/browse/CASSANDRA-16649?focusedCommentId=17341901&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17341901] and the comment after it. I'm not confident yet of any other approach but the "throwaway" commits introducing the snapshot repository in patches (which are akin to the circle "throwaway" commits). > 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
[jira] [Comment Edited] (CASSANDRA-17050) Upgrade tests fail with InvocationTargetException
[ https://issues.apache.org/jira/browse/CASSANDRA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435487#comment-17435487 ] Benedict Elliott Smith edited comment on CASSANDRA-17050 at 10/28/21, 3:15 PM: --- Additional necessary changes to [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. was (Author: benedict): [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
