[jira] [Commented] (CASSANDRA-15901) Fix unit tests to load test/conf/cassandra.yaml (so to listen on a valid ip)

["Berenguer Blasi (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-15901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148621#comment-17148621 ] 

Berenguer Blasi commented on CASSANDRA-15901:
---------------------------------------------

The latest run with the latest commit looks ok imo:
 * [CI j11|https://app.circleci.com/pipelines/github/bereng/cassandra/52/workflows/573ad5be-e34d-4668-a0af-2726d4b35568] Failure seems unrelated and passes locally
 * [CI j8|https://app.circleci.com/pipelines/github/bereng/cassandra/52/workflows/16e15155-7dce-4877-86f5-315c6a837d36] Seems to be a new flaky test but unrelated to the PR imo. It passes when ran locally but failed once locally on {{ant test}}
 * The [latest|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/156/] ci-cassandra run looks much better but:
 ** ActiveRepairServiceTest could be a [legit|https://ci-cassandra.apache.org/job/Cassandra-trunk/199/testReport/org.apache.cassandra.service/ActiveRepairServiceTest/testQueueWhenPoolFullStrategy_cdc/history/] flaky
 ** ClearSpanshotTest passes locally and it failed with some weird VM error :shrug:
 ** Connection tests have given timeouts [before|https://ci-cassandra.apache.org/job/Cassandra-trunk/199/testReport/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_cdc/history/]

It would be good to have a second opinion here. But I think the failures we are hitting are legit flaky tests now that we've removed much of the noise. [~mck] would you be so kind to run the tests again but not on cassandra13 to see what happens? I think we can then move this to review if no weird stuff happens. Wdyt?

> Fix unit tests to load test/conf/cassandra.yaml (so to listen on a valid ip)
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15901
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15901
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0-rc
>
>
> Many of the ci-cassandra jenkins runs fail on {{ip-10-0-5-5: Name or service not known}}. CASSANDRA-15622 addressed some of these but many still remain. Currently test C* nodes are either failing or listening on a public ip depending on which agent they end up.
> The idea behind this ticket is to make ant force the private VPC ip in the cassandra yaml when building, this will force the nodes to listen on the correct ip.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org