When provided with test time estimates Bluepill calculates the total estimated execution time and splits the test bundles to try and get optimal concurrency. However, if the total estimated execution time is zero for some reason, then the logic fails to split bundles and gets trapped in an infinite loop. The reasons for zero estimated time could be...
The test names are not read correctly (Eg. the () that are added as a suffix for swift test names in recent Xcode release)
None of the tests in a set has estimated times or have 0 sec estimates.
This issue is a tracker to fix that bug. \cc @ob @chenxiao0228
When provided with test time estimates Bluepill calculates the total estimated execution time and splits the test bundles to try and get optimal concurrency. However, if the total estimated execution time is zero for some reason, then the logic fails to split bundles and gets trapped in an infinite loop. The reasons for zero estimated time could be...
()
that are added as a suffix for swift test names in recent Xcode release)0 sec
estimates.This issue is a tracker to fix that bug. \cc @ob @chenxiao0228