[
https://issues.apache.org/jira/browse/CASSANDRA-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525641#comment-17525641
]
Brandon Williams commented on CASSANDRA-17565:
----------------------------------------------
bq. but that didn't work, so ignore this.
To clarify, there are 7 failures in that run, but 6 were git errors and one was
legit.
Not trusting the results, I did another [4000
runs|https://app.circleci.com/pipelines/github/driftx/cassandra/443/workflows/8e7a307a-4a13-4c00-ab45-ca65b48ac602/jobs/5184]
and got one failure again...however, examining the line number, that has to be
from the 4.0 side, and indeed it needs the same patch. But now the question
is, can the upgrade test be run with both a custom 4.0 and trunk branch? If
not, perhaps this is enough to commit the trunk side, and then we can run 4k
with a custom 4.0 branch against it, which should prove out the whole thing.
> Fix test_parallel_upgrade_with_internode_ssl
> --------------------------------------------
>
> Key: CASSANDRA-17565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17565
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.x
>
>
> While working on CASSANDRA-17341 I hit this flaky test, very rarely failing
> but it is failing on trunk.
> More info in this CI run:
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1563/workflows/61bda0b7-f699-4897-877f-c7d523a03127/jobs/10318
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
