[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311854#comment-15311854
]
Robert Stupp commented on CASSANDRA-11663:
--
Yes, this could have happened before
[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310608#comment-15310608
]
Yuki Morishita commented on CASSANDRA-11663:
I think this is also fixed by
[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297303#comment-15297303
]
Jim Witschey commented on CASSANDRA-11663:
--
For testing this for the 3.6 release, check out
[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297102#comment-15297102
]
Jim Witschey commented on CASSANDRA-11663:
--
Failures on the 3.6 release-checking job:
[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274932#comment-15274932
]
Russ Hatch commented on CASSANDRA-11663:
looks to be happening on 3.0.x too
> dtest failure
[
https://issues.apache.org/jira/browse/CASSANDRA-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258750#comment-15258750
]
Russ Hatch commented on CASSANDRA-11663:
looks like maybe a timeout issue. look to be failing