[
https://issues.apache.org/jira/browse/FLINK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583497#comment-16583497
]
ASF GitHub Bot commented on FLINK-10159:
----------------------------------------
pnowojski commented on issue #6570: [FLINK-10159][tests] Fail
TestHarness.initializeState if harness has already been initialized
URL: https://github.com/apache/flink/pull/6570#issuecomment-413782923
Thanks! Merged.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> TestHarness#initializeState(xyz) calls after TestHarness#open() are being
> silently ignored
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-10159
> URL: https://issues.apache.org/jira/browse/FLINK-10159
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.6.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Critical
> Labels: pull-request-available
>
> This is an old issue. Incorrect order of initializeState and open result to
> initializeState being ignored. For example in this code:
> {code:java}
> testHarness = createTestHarness(topic);
> testHarness.setup();
> testHarness.open();
> testHarness.initializeState(snapshot1);
> {code}
> Which is miss-leading both for Flink developers and for users (since we
> recommend using test harness for unit tests).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
