You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using dynamic parallel via TEST_TIME, there is a chance that we do not get the actual test execution time. This could result in default test execution being used (2 secs per test). In the following example, extended.jck is expected to be complete in 01m56s on one machine.
00:05:04.866 TEST DURATION
00:05:04.866 ====================================================================================
00:05:04.866 Total number of tests searched: 94
00:05:04.866 Number of test durations found: 94
00:05:04.866 Top slowest tests:
00:05:04.866 00m02s jck-compiler-lang-CLSS-Group9_0
00:05:04.866 00m02s jck-compiler-lang-ANNOT_0
00:05:04.866 00m02s jck-runtime-lang-EXEC_0
00:05:04.866 ====================================================================================
00:05:04.866
00:05:04.866 Test target is split into 1 lists.
00:05:04.866 Reducing estimated test running time from 01m56s to 01m56s.
00:05:04.866
00:05:04.866 -------------------------------------testList_0-------------------------------------
00:05:04.866 Number of tests: 94
00:05:04.866 Estimated running time: 01m56s
This may be due to network issues. While we are investigating this, we should set the default minimal NUM_MACHINES for certain long-running test builds when dynamic parallel via TEST_TIME is used.
The text was updated successfully, but these errors were encountered:
When using dynamic parallel via TEST_TIME, there is a chance that we do not get the actual test execution time. This could result in default test execution being used (2 secs per test). In the following example, extended.jck is expected to be complete in 01m56s on one machine.
link
This may be due to network issues. While we are investigating this, we should set the default minimal NUM_MACHINES for certain long-running test builds when dynamic parallel via TEST_TIME is used.
The text was updated successfully, but these errors were encountered: