All, There is an upper bound for job execution time on free workers (set to 6 hours max[1]), which can be configured beyond 6hrs with a self-hosted worker. All of our pipeline jobs are using `--max-workers` to parallelize gradle tasks but `testMaxParallelForks` is left to default which is (1/4th of the available CPU cores), so primarily due to running only a single test in each parallel fork geode-core distribution tests are taking more than 6 hours. Other than finding a solution for core distributed tests, most DUnit tests are passed[2] by splitting them into individual jobs (WAN, CQ, Lucene, assembly, management).
Will reach out to infra team and trying playing with `--max-workers` to parallelize more tests than having to run parallel tests with in a fork would be options. I am going to wait for few days to get answers from infra team before I can create a PR to add at least the passing DUnits. [1] https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration [2] https://github.com/apache/geode/actions/runs/4639012912 Sai
