From d5533c00d609a73847d06d25f4396c42abc69ae6 Mon Sep 17 00:00:00 2001
From: Adria Navarro <adria@budibase.com>
Date: Fri, 28 Jul 2023 12:53:52 +0200
Subject: [PATCH] Fix workerIdleMemoryLimit usage

---
 packages/server/jest.config.ts  | 1 -
 packages/server/scripts/test.sh | 4 ++--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/packages/server/jest.config.ts b/packages/server/jest.config.ts
index 87e2ef4d0a..f36864f999 100644
--- a/packages/server/jest.config.ts
+++ b/packages/server/jest.config.ts
@@ -16,7 +16,6 @@ const baseConfig: Config.InitialProjectOptions = {
     "@budibase/shared-core": "<rootDir>/../shared-core/src",
     "@budibase/types": "<rootDir>/../types/src",
   },
-  workerIdleMemoryLimit: "2GB",
 }
 
 // add pro sources if they exist
diff --git a/packages/server/scripts/test.sh b/packages/server/scripts/test.sh
index 353995f8bb..a2c6f2cdf2 100644
--- a/packages/server/scripts/test.sh
+++ b/packages/server/scripts/test.sh
@@ -6,8 +6,8 @@ then
   # --runInBand performs better in ci where resources are limited
   export NODE_OPTIONS="--max-old-space-size=4096"
   node ../../node_modules/jest/bin/jest.js --version
-  echo "node --expose-gc --no-compilation-cache ../../node_modules/jest/bin/jest.js --runInBand --logHeapUsage --forceExit"
-  node --expose-gc --no-compilation-cache ../../node_modules/jest/bin/jest.js --runInBand --logHeapUsage --forceExit
+  echo "jest --coverage --maxWorkers=2 --forceExit"
+  jest --coverage --maxWorkers=2 --forceExit --workerIdleMemoryLimit=2000MB
 else
   # --maxWorkers performs better in development
   echo "jest --coverage --maxWorkers=2 --forceExit"