[
https://issues.apache.org/jira/browse/SAMZA-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961256#comment-13961256
]
Chris Riccomini commented on SAMZA-224:
---------------------------------------
Hmm, this is scary. Thanks for looking into this. I think it's just as likely
that the test itself is messed up, but I've also seen this test catch some very
subtle bugs.
In the past, when I've had these issues, turning on debug, and painfully
walking through the debug logs has exposed the problem. That said, it's VERY
verbose in debug mode, and there are some debug stuff that should be trace
(probably worth a separate JIRA).
Might also be that some state is persisted, somewhere (/tmp?) or a process is
leaked (ZK/Kafka)? All this stuff *should* be randomized (ports and
directories) to avoid collisions between runs, but maybe we missed something.
> TestStatefulTask.testShouldStartAndRestore fails intermittently
> ---------------------------------------------------------------
>
> Key: SAMZA-224
> URL: https://issues.apache.org/jira/browse/SAMZA-224
> Project: Samza
> Issue Type: Bug
> Reporter: Martin Kleppmann
>
> [~closeuris] reported the following issue on SAMZA-185. I'm now
> intermittently seeing this problem too, so I'm opening a new issue for it (as
> I'm not sure the issue has anything to do with the Kafka 0.8.1 upgrade).
> {noformat}
> org.apache.samza.test.integration.TestStatefulTask >
> testShouldStartAndRestore FAILED
> java.lang.AssertionError at TestStatefulTask.scala:356
> 2 tests completed, 1 failed
> :samza-test_2.10:test FAILED
> {noformat}
> Logs provided by Yan (mine look similar):
> Failed tests: http://pastebin.com/3nEDw9jC
> Standard output: http://pastebin.com/20vZbk7c
> Standard error: http://pastebin.com/gU6cTNAr
--
This message was sent by Atlassian JIRA
(v6.2#6252)
