[
https://issues.apache.org/jira/browse/CASSANDRA-10517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955822#comment-14955822
]
Joshua McKenzie commented on CASSANDRA-10517:
---------------------------------------------
>From [build
>#54|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_utest_win32/54/testReport/org.apache.cassandra.cql3/ViewTest/testCollections/]:
{noformat}
org.apache.cassandra.cql3.ViewTest.testCollections
Timeout occurred. Please note the time in the report does not reflect the time
until the timeout.
{noformat}
Looks like we have a variety of tests in ViewTest that are timing out, hence
the sporadic reporting for other tests in the package.
> Make sure all unit tests run on CassCI on Windows
> -------------------------------------------------
>
> Key: CASSANDRA-10517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10517
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Labels: triage
> Fix For: 3.0.0 rc2
>
>
> It seems that some Windows unit tests aren't run sometimes on CassCI, and
> there's no error reporting for this. For instance, this test was introduced
> around the time build #38 would have happened, but has only run in builds
> #50-3 and #64:
> http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_utest_win32/lastCompletedBuild/testReport/org.apache.cassandra.cql3/ViewTest/testPrimaryKeyIsNotNull/history/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
