Add Path argument to supportsModifications, supports*LinksNatively.

This works better with UnionFileSystem, as (eg.) different mapped file systems might not agree on whether they are read-only.

No actual code changes have been made that actually uses this argument, so this should be a behaviour no-op.

PiperOrigin-RevId: 172782759

1 files changed, 2 insertions, 2 deletions

diff --git a/src/test/java/com/google/devtools/build/lib/vfs/UnionFileSystemTest.java b/src/test/java/com/google/devtools/build/lib/vfs/UnionFileSystemTest.java
index 780a529e87..0c8cf77360 100644
--- a/src/test/java/com/google/devtools/build/lib/vfs/UnionFileSystemTest.java
+++ b/src/test/java/com/google/devtools/build/lib/vfs/UnionFileSystemTest.java
@@ -136,8 +136,8 @@ public class UnionFileSystemTest extends SymlinkAwareFileSystemTest {
   // read-only, even if the delegate filesystems are read/write.
   @Test
   public void testModificationFlag() throws Exception {
-    assertThat(unionfs.supportsModifications()).isTrue();
     Path outPath = unionfs.getPath("/out/foo.txt");
+    assertThat(unionfs.supportsModifications(outPath)).isTrue();
     assertThat(unionfs.createDirectory(outPath.getParentDirectory())).isTrue();
     OutputStream outFile = unionfs.getOutputStream(outPath);
     outFile.write('b');
@@ -148,7 +148,7 @@ public class UnionFileSystemTest extends SymlinkAwareFileSystemTest {
     // Note that this does not destroy the underlying filesystems;
     // UnionFileSystem is just a view.
     unionfs = createDefaultUnionFileSystem(true);
-    assertThat(unionfs.supportsModifications()).isFalse();
+    assertThat(unionfs.supportsModifications(outPath)).isFalse();
 
     InputStream outFileInput = unionfs.getInputStream(outPath);
     int outFileByte = outFileInput.read();