You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/05/31 13:21:12 UTC

[jira] [Closed] (FLINK-3607) Decrease default forkCount for tests

     [ https://issues.apache.org/jira/browse/FLINK-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maximilian Michels closed FLINK-3607.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Defaulting to the saner {{1C}} with bcf5f4648670770b6c5fcfd56fd24660fae5ad44

> 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
>             Fix For: 1.1.0
>
>
> 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)