Removed the gradlew --stop from the transforms caching experiment scr…

…ipt, as that's not needed anymore since we're running with --no-daemon
gradle · Sep 17, 2024 · 362bbd3 · 362bbd3
1 parent 64e1be0
commit 362bbd3
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 3 deletions.
diff --git a/transforms-caching-experiment/README.md b/transforms-caching-experiment/README.md
@@ -14,8 +14,6 @@ You can then use the published build scans to evaluate how caching artifact tran
 
 If results show that (remote) caching of transforms is not beneficial for your project, you can disable caching for (specific) transforms using the flags in this script.
 
-Note: Killing all gradle daemons is necessary for the experiments to give conclusive results. This may impact your ongoing work, so it is recommended to pause other work while the script is running.
-
 ## Requirements
 
 - A Develocity instance to publish scans to

diff --git a/transforms-caching-experiment/remote-cache-experiment-transforms.sh b/transforms-caching-experiment/remote-cache-experiment-transforms.sh
@@ -66,7 +66,6 @@ do
         echo "Test caches/*/transforms removal with $args"
         echo "------------------------------------------------------------"
         set -x
-        ./gradlew --stop
 
         echo "Removing transforms from $homeDir/caches"
         rm -rf $homeDir/caches/*/transforms