Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
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.