[
https://issues.apache.org/jira/browse/CASSANDRA-16515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300344#comment-17300344
]
Brandon Williams commented on CASSANDRA-16515:
----------------------------------------------
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/479/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/479/pipeline]
> Don't fail all ViewFilteringTest cases because one case timed out
> -----------------------------------------------------------------
>
> Key: CASSANDRA-16515
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16515
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When {{ViewFilteringTest}} creates a view, it is added to the list of created
> views. Those views are removed after each test cases. If creating a view
> fail, it is not added to the list of views to be dropped because the
> assumption is that when the command fails, the view should not be created.
> This is ok in general however it is not a valid assumption when we get
> operation timed out because we cannot say anything about its real result.
> This way, it is possible that the view gets created, the driver throws time
> out and we do not remove the created view. All other test cases which tries
> to create that view will fail because the view already exists.
> While it seems very improbable, we actually hit this a couple of times on our
> infrastructure
> !screenshot-1.png!
> !screenshot-2.png!
> !screenshot-3.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
