[jira] [Commented] (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=17441039#comment-17441039 ] Michael Semb Wever commented on CASSANDRA-17050: dtest-api-0.0.11 has passed vote and been published. > 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.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (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=17436550#comment-17436550 ] Michael Semb Wever commented on CASSANDRA-17050: Something broke python dtests on the 11th October. It wasn't this ticket, nor does it look like CASSANDRA-16839 or its [commit|https://github.com/apache/cassandra-dtest/commit/7c958e2b2bd53018a50ab1f529e1a2cca173]. And it's not flakies, a ton definitely broke for good :( > 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] [Commented] (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=17436490#comment-17436490 ] Benedict Elliott Smith commented on CASSANDRA-17050: Something is very badly wrong with CI, I see several hundred python dtest failures in CircleCI for [17050-4.0|https://app.circleci.com/pipelines/github/belliottsmith/cassandra/124/workflows/4bcc17bb-01e8-4cb3-81f1-e64a3e0e323e]. I can't imagine how this patch could have caused these, as the 4.0 branch literally only changes the java dtests, but I will run a baseline test for each of the branches for comparison to be sure. > 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] [Commented] (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=17436364#comment-17436364 ] Michael Semb Wever commented on CASSANDRA-17050: Happy to ignore if they are not jvm-dtest* related. Logs are available. See the Console Output first (if from the pipeline you need to click on one of the links to the inner stage job's Console Output), then at the bottom (or search for 'For test report and logs') there's a link to nightlies.a.o where test logs are uploaded. > 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] [Commented] (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=17436362#comment-17436362 ] Benedict Elliott Smith commented on CASSANDRA-17050: Can we get the test logs on Jenkins? FWIW, it looks like a significant portion are: python auth dtests, python upgrade dtests. > 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] [Commented] (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=17436361#comment-17436361 ] Benedict Elliott Smith commented on CASSANDRA-17050: None of the failures I'm seeing are related to in-jvm upgrade tests anymore? It's possible we've somehow broken normal dtests, or that they've been broken by some other issue. I'll take a look at the output. > 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] [Commented] (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=17436360#comment-17436360 ] Michael Semb Wever commented on CASSANDRA-17050: [~benedict], I'm not seeing those fixes in ci-cassandra yet, to the contrary more failures. Am I doing something wrong here…? > 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] [Commented] (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 commented on CASSANDRA-17050: 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] [Commented] (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=17435931#comment-17435931 ] Benedict Elliott Smith commented on CASSANDRA-17050: I just wonder if we should consider nested git repositories containing the library code, or some other approach to reduce the friction. This will become more acute over time as Accord will want to use the utilities from Cassandra (so that it's consistent with it), so we might end up with three or more projects that are dependencies for building Cassandra, so it feels like we should aim to support them all within the same IDE and commit flow. I guess I should raise a DISCUSS thread about it. > 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] [Commented] (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=17435930#comment-17435930 ] Michael Semb Wever commented on CASSANDRA-17050: bq. So is the idea that we'll merge with a SNAPSHOT dependency, or that we'll first release dtest-api? That we'll first release dtest-api. I know it's not ideal, we can revisit this, though one can say it fits into a stable trunk practice, but it is overhead… > 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] [Commented] (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=17435928#comment-17435928 ] Benedict Elliott Smith commented on CASSANDRA-17050: So is the idea that we'll merge with a SNAPSHOT dependency, or that we'll first release dtest-api? I can look into modifying build.xml to use different dependencies for release, though we end up in a weird release chain where we cannot release cassandra without first releasing dtest-api (and any other dependencies). I'll merge dtest-api changes for now anyway, thanks. > 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] [Commented] (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=17435668#comment-17435668 ] Michael Semb Wever commented on CASSANDRA-17050: bq. Additional necessary changes to dtest-api +1 And i reckon the "update SNAPSHOT" commit should be ninja'd to trunk. That was supposed to have happened in [2139b4c85e319b17afbdea2f653152d1e1895fc6|https://github.com/apache/cassandra-in-jvm-dtest-api/commit/2139b4c85e319b17afbdea2f653152d1e1895fc6]. > 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] [Commented] (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 commented on CASSANDRA-17050: 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] [Commented] (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 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
[jira] [Commented] (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=17433726#comment-17433726 ] Benedict Elliott Smith commented on CASSANDRA-17050: It looks like there's another [unrelated issue|https://app.circleci.com/pipelines/github/belliottsmith/cassandra/113/workflows/1f672000-5432-44d7-a691-b1d397c40932/jobs/3866/tests#failed-test-5] This might require an update to dtest-api, I'm investigating > 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] [Commented] (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=17433721#comment-17433721 ] Michael Semb Wever commented on CASSANDRA-17050: CI - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1243/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1243/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1241/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1241/] - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1240/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1240/] - 3.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1239/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1239/] - 2.2 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1238/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1238/] > 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] [Commented] (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=17433670#comment-17433670 ] Michael Semb Wever commented on CASSANDRA-17050: That discussion (which is out of scope) is ongoing. pre-release check is no good, we want a faster feedback on such CVE breakages. part of the problem is the check can fail for one of three reasons: # a new dependency is introduced in the patch, and that should be caught (not merged) # a new CVE is listed, and that breaks all our CI # the nist.gov becomes unavailable, and that breaks all our CI. We want (1) as part of CI. We want (2) as feedback as fast as possible, but not breaking CI. We want to ignore (workaround) (3). > 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] [Commented] (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=17433661#comment-17433661 ] Benedict Elliott Smith commented on CASSANDRA-17050: FWIW, the dependency check fails locally for unrelated reasons, seemingly unable to connect to nist.gov, though I am able to connect to nist.gov just fine and download the file it is looking for. So perhaps this check has some kinks to work out before we depend upon it. I'm also unconvinced of the sense of downloading an arbitrary binary direct from somebody's personal GitHub to execute on the local machine. I'm not convinced of the sense of breaking builds that previously worked for this check, it should at most be a pre-release check rather than a pre-merge check. Perhaps it could also be pre-merge if build.xml modified as part of the patch. > 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] [Commented] (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=17433657#comment-17433657 ] Benedict Elliott Smith commented on CASSANDRA-17050: That isn't related to this patch. > 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] [Commented] (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=17433609#comment-17433609 ] Michael Semb Wever commented on CASSANDRA-17050: The patches don't build, because they don't pass the `ant dependency-check` which now fail on all branches because of a new CVE in netty-all-4.0.44.Final.jar > 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] [Commented] (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=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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
