Thread FileSystem through to a single Path#delete call site.

This requires a fairly large amount of changes to fundamental objects like BlazeRuntime, Executor, and so on, as well as changing a lot of test code to thread the file system through. I expect future CLs to be much smaller.

PiperOrigin-RevId: 173678144

1 files changed, 2 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/profiler/memory/AllocationTrackerModule.java b/src/main/java/com/google/devtools/build/lib/profiler/memory/AllocationTrackerModule.java
index 4a503e44ba..72f1fe1413 100644
--- a/src/main/java/com/google/devtools/build/lib/profiler/memory/AllocationTrackerModule.java
+++ b/src/main/java/com/google/devtools/build/lib/profiler/memory/AllocationTrackerModule.java
@@ -22,6 +22,7 @@ import com.google.devtools.build.lib.runtime.BlazeModule;
 import com.google.devtools.build.lib.runtime.BlazeRuntime;
 import com.google.devtools.build.lib.runtime.WorkspaceBuilder;
 import com.google.devtools.build.lib.syntax.Callstack;
+import com.google.devtools.build.lib.vfs.FileSystem;
 import com.google.devtools.common.options.OptionsProvider;
 import java.util.UUID;
 
@@ -57,6 +58,7 @@ public class AllocationTrackerModule extends BlazeModule {
       OptionsProvider startupOptions,
       BlazeVersionInfo versionInfo,
       UUID instanceId,
+      FileSystem fileSystem,
       ServerDirectories directories,
       Clock clock) {
     String memoryTrackerPropery = System.getProperty("RULE_MEMORY_TRACKER");