[
https://issues.apache.org/jira/browse/CASSANDRA-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016575#comment-14016575
]
Joshua McKenzie commented on CASSANDRA-7334:
--------------------------------------------
Hm. Unfortunate that infinite loop in a test means we don't get stderr or
stdout redirected and flushed - that doesn't help in the troubleshooting
process that much now does it.
bq. FSWriteError thrown by CommitLogSegment() is not caught in
CommitLogSegmentManager() and many other places which led not to detect the
failure of this issue. Is this the intended behavior?
We want these exceptions to bubble up and show on the root level log. In this
context, I believe the infinite loop / kill via timeout on this test caused us
not to see the output.
SchemaLoader is used only in testing code (or stress) so modifications there
should be limited in scope to non-production code. Pending confirmation on
linux tests succeeding, LGTM.
> 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
>
> Attachments: CASSANDRA-7334.diff
>
>
> 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)
