in a PR to ATHs it will try to split tests based on previous runs if the run is not build#1 of the PR.

however in the case the first build did not succeed, (and there are not successful builds) then as configured it createts 10 splits but will not create an exclusion file as there where no successful jobs (it was unstable).

this results in running each test 20 times (as a minumim) once in each split (ten) for each of java8 and java11. (I say at least as we also re-run flaky tests which is in the opinion oif this user not a good practice and allows these flakes to creep in and consume even more resources),