[
https://issues.apache.org/jira/browse/CASSANDRA-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015912#comment-14015912
]
Joshua McKenzie commented on CASSANDRA-7334:
--------------------------------------------
Unit tests aren't generating a system.log for me, and an exception like that
should bubble up and report on the test failure to stdout/stderr. Maybe try
dumping a jstack every second against the running process and/or profiling the
running test (with something like jvisualvm) to try and get a clear picture of
where the test is spinning? Looks like it's pegging out a cpu during the test
so it's definitely busy doing something.
> RecoveryManagerTest times out on Windows
> ----------------------------------------
>
> Key: CASSANDRA-7334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7334
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Joshua McKenzie
> Assignee: Ala' Alkhaldi
> Priority: Minor
> Labels: Windows
> Fix For: 3.0
>
>
> Takes 11 seconds on a slow linux vm to pass, times out on Windows.
> {code:title=timeout message}
> [junit] Testcase:
> org.apache.cassandra.db.RecoveryManagerTest:testRecoverCounter: Caused an
> ERROR
> [junit] Timeout occurred. Please note the time in the report does not
> reflect the time until the timeout.
> [junit] junit.framework.AssertionFailedError: Timeout occurred. Please
> note the time in the report does not reflect the time until the timeout.
> [junit]
> [junit]
> [junit] Test org.apache.cassandra.db.RecoveryManagerTest FAILED (timeout)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
