I see that there is at least one person concerned about DUnit tests
requiring longer timeouts. This is the current situation with an unknown
number of the DUnit tests. One possibility is to move the worst offenders
to a new src set within geode-core and then give that its own job with a
larger time
Is the coreDistributedTests the only dunit job that currently takes too
long? If it is we may want to split that into more than one job.
-Kirk
On Wed, Apr 12, 2023 at 7:58 PM Sai Boorlagadda
wrote:
> All,
>
> There is an upper bound for job execution time on free workers (set to 6
> hours max[1
