[
https://issues.apache.org/jira/browse/FLINK-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191031#comment-15191031
]
Maximilian Michels commented on FLINK-3607:
-------------------------------------------
Sure, you can set {{-Dflik.forkCount=1C}} but I think we should provide a
sensible default. It seems like that our tests have grown too complex for the
current forkCount and we need to change the default value. My system, for
instance, can't build with 1.5C, equivalent to 12 concurrent test threads (8
virtual cores).
> Decrease default forkCount for tests
> ------------------------------------
>
> Key: FLINK-3607
> URL: https://issues.apache.org/jira/browse/FLINK-3607
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Labels: test-stability
>
> I'm seeing many tests failures because of timeouts:
> https://builds.apache.org/job/flink-ci/1/testReport/
> The {{forkCount}} is set to the aggressive value {{1.5C}}. We should consider
> to reduce it at least to {{1C}} (1 fork per exposed physical/virtual core).
> That could improve the test stability.
> I did another test using {{1C}} on Jenkins and had only one failed test and a
> decreased (!) run time: https://builds.apache.org/job/flink-ci/2/testReport/
> 1.5C: 1h 57m
> 1C: 1h 35m
> I'll run some more tests to verify this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
