[
https://issues.apache.org/jira/browse/FLINK-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TisonKun updated FLINK-11397:
-----------------------------
Description:
Currently Kafka connector tests are unbearably slow, which is tracked by
FLINK-10603. With investigation, the construction and initialization of
{{AbstractStreamOperatorTestHarness}} is quite slow.
-When walk down the code, it amazed me that {{mockTask =
mock(StreamTask.class);}} cost a few of second to finish. If we can introduce a
test class instead of mock framework, the situation might be loosen.-
cc [~Zentol] [~pnowojski]
was:
Currently Kafka connector tests are unbearably slow, which is tracked by
FLINK-10603. With investigation, the construction and initialization of
{{AbstractStreamOperatorTestHarness}} is quite slow.
When walk down the code, it amazed me that {{mockTask =
mock(StreamTask.class);}} cost a few of second to finish. If we can introduce a
test class instead of mock framework, the situation might be loosen.
cc [~Zentol] [~pnowojski]
> Speed up initialization of AbstractStreamOperatorTestHarness
> ------------------------------------------------------------
>
> Key: FLINK-11397
> URL: https://issues.apache.org/jira/browse/FLINK-11397
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 1.8.0
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
>
> Currently Kafka connector tests are unbearably slow, which is tracked by
> FLINK-10603. With investigation, the construction and initialization of
> {{AbstractStreamOperatorTestHarness}} is quite slow.
> -When walk down the code, it amazed me that {{mockTask =
> mock(StreamTask.class);}} cost a few of second to finish. If we can introduce
> a test class instead of mock framework, the situation might be loosen.-
> cc [~Zentol] [~pnowojski]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
