Skip to content
Discussion options

You must be logged in to vote

For anyone else w/ a similar issue, this seems to have fixed it for us for now. Reduced parallelism in CI and increased corePoolSize.

runner {
    parallel {
        // see https://spockframework.org/spock/docs/2.3/parallel_execution.html
        enabled(true)
        defaultSpecificationExecutionMode('CONCURRENT')
        defaultExecutionMode('SAME_THREAD')

        // see spock.config.ParallelConfiguration
        int availableProcessors = Runtime.getRuntime().availableProcessors()
        // Spock defaults parallelism to availableProcessors - 2
        // In CI environments, be more conservative to avoid thread exhaustion
        int parallelism = System.getenv('CI')
            ? Math.m…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by efenderbosch-atg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants