adelapena commented on pull request #493:
URL: https://github.com/apache/cassandra/pull/493#issuecomment-638214216


   These are the CI results after rebasing everything:
   
   | branch | CircleCI | cassandra-ci utest | cassandra-ci dtest |
   |--------|---------|--------------------|--------------------|
   
|3.0|[48](https://app.circleci.com/pipelines/github/adelapena/cassandra/48/workflows/fcb8e1ab-545a-47f2-9432-03b783953f88)|[113](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-test/113/)|[141](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/141/)|
   
|3.11|[49](https://app.circleci.com/pipelines/github/adelapena/cassandra/49/workflows/894eb560-45c9-44a9-b48b-6ed2f47b2298)|[114](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-test/114/)|[142](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/142/)|
   
|trunk|[50](https://app.circleci.com/pipelines/github/adelapena/cassandra/50/workflows/0fa01053-2b96-4880-afb2-d8fe020b8848)|[115](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-test/115/)|[143](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/143/)|
   
   It seems that `test_dead_sync_initiator ` still fails for some runs after 
rebasing 
([here](https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/143/testReport/junit/dtest.repair_tests.repair_test/TestRepair/test_dead_sync_initiator/)
 and 
[here](https://app.circleci.com/pipelines/github/adelapena/cassandra/50/workflows/0fa01053-2b96-4880-afb2-d8fe020b8848/jobs/409)),
 although I don't think it's related to the changes introduced by this PR. I 
haven't been able to reproduce the failure locally.
   
   There is also [a failure in 
`CustomIndexTest.testFailing2iFlush`](https://app.circleci.com/pipelines/github/adelapena/cassandra/50/workflows/0fa01053-2b96-4880-afb2-d8fe020b8848/jobs/404)
 in the CircleCI run for 8272-trunk. Multiplexer runs show that this test is 
slightly flaky in 8272-trunk, whereas it looks stable in trunk:
   | branch | run | iterations|failures |
   |--------|-----|----------|-|
   
|trunk|[653](https://jenkins-cassandra.datastax.lan/job/parameterized-testall/653/)|200|0|
   
|trunk|[654](https://jenkins-cassandra.datastax.lan/job/parameterized-testall/654/)|200|0|
   
|8272-trunk|[652](https://jenkins-cassandra.datastax.lan/job/parameterized-testall/652/)|100|1|
   
|8272-trunk|[655](https://jenkins-cassandra.datastax.lan/job/parameterized-testall/655/)|200|2|
   
   That test uses indexes but not in through read path nor with multiple nodes, 
so I don't know how the failure can be caused by this PR. I'll try to reproduce 
it locally, and make sure it doesn't really affect trunk.
   
   @jasonstack other than that, do you agree to applying replica filtering 
protection with transient replicas?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org
For additional commands, e-mail: pr-h...@cassandra.apache.org

Reply via email to