flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3607) Decrease default forkCount for tests
Date Fri, 11 Mar 2016 14:47:48 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191019#comment-15191019

Robert Metzger commented on FLINK-3607:

I think you can pass a custom fork count using maven properties if a build environment is
not capable of handling the parallelism.

> 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
> 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

View raw message