From 7cbf8a1f7d753028b82d4facc56430dad8336f78 Mon Sep 17 00:00:00 2001
From: David Allison <62114487+david-allison@users.noreply.github.com>
Date: Wed, 31 Jan 2024 03:27:08 +0000
Subject: [PATCH] build(ci): remove IN_PROCESS compiler execution strategy

Added in f5ecb05efc3117238cbd42935542176d4436ee5f
Related: 655516582cbee7dffb70a3be6318103731f9b9a0

ref: https://github.com/ankidroid/Anki-Android/pull/11341#issuecomment-1129119319

but CI runners now have 16GB RAM, so this is not necessary any more

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories

Issue 15368
---
 build.gradle | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/build.gradle b/build.gradle
index 157c55d50246..b4afb04aaaf8 100644
--- a/build.gradle
+++ b/build.gradle
@@ -140,13 +140,6 @@ ext {
         // Which is 1:1 https://docs.microsoft.com/en-gb/azure/virtual-machines/acu : DS1_v2 - DS15_v2 | 1:1
         gradleTestMaxParallelForks = 2
 
-        // separate gradle compile process is a major speed improvement, but consumes 2x RAM
-        // the CI machines don't have enough RAM to do that without going in to swap quite a bit
-        // so for CI machines only - to improve reliability despite compilation speed hit, compile kotlin in process
-        println "CI build detected: setting compiler execution strategy to IN_PROCESS"
-        tasks.withType(KotlinCompile).configureEach {
-            compilerExecutionStrategy.set(KotlinCompilerExecutionStrategy.IN_PROCESS)
-        }
     } else {
         // Use 50% of cores to account for SMT which doesn't help this workload
         gradleTestMaxParallelForks = Runtime.runtime.availableProcessors().intdiv(2) ?: 1