`Microsoft.Extensions.FileProviders.Physical.Tests` test fails with `System.UnauthorizedAccessException`

[radical]

Test failed on runtime (Libraries Test Run release coreclr windows x64 Debug), for #56769

Build
Log

Microsoft.Extensions.FileProviders.PhysicalFileProviderTests.UsePollingFileWatcher_UseActivePolling_HasChanged_SymbolicLink_TargetChanged(useWildcard: False, linkWasBroken: False) [FAIL]
      System.UnauthorizedAccessException : Access to the path 'C:\h\w\ABC3094B\t\y5tfj3va.j2q\y4b1rsjy.300' is denied.
      Stack Trace:
        /_/src/libraries/Common/src/Interop/Windows/Kernel32/Interop.CreateSymbolicLink.cs(60,0): at Interop.Kernel32.CreateSymbolicLink(String symlinkFileName, String targetFileName, Boolean isDirectory)
        /_/src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs(423,0): at System.IO.FileSystem.CreateSymbolicLink(String path, String pathToTarget, Boolean isDirectory)
        /_/src/libraries/System.Private.CoreLib/src/System/IO/File.cs(1026,0): at System.IO.File.CreateSymbolicLink(String path, String pathToTarget)
        /_/src/libraries/Microsoft.Extensions.FileProviders.Physical/tests/PhysicalFileProviderTests.netcoreapp.cs(104,0): at Microsoft.Extensions.FileProviders.PhysicalFileProviderTests.UsePollingFileWatcher_UseActivePolling_HasChanged_SymbolicLink_TargetChanged(Boolean useWildcard, Boolean linkWasBroken)
        --- End of stack trace from previous location ---

Tagging subscribers to this area: @maryamariyan, @dotnet/area-extensions-filesystem
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Test failed on runtime (Libraries Test Run release coreclr windows x64 Debug), for #56769

Build
Log

Microsoft.Extensions.FileProviders.PhysicalFileProviderTests.UsePollingFileWatcher_UseActivePolling_HasChanged_SymbolicLink_TargetChanged(useWildcard: False, linkWasBroken: False) [FAIL]
      System.UnauthorizedAccessException : Access to the path 'C:\h\w\ABC3094B\t\y5tfj3va.j2q\y4b1rsjy.300' is denied.
      Stack Trace:
        /_/src/libraries/Common/src/Interop/Windows/Kernel32/Interop.CreateSymbolicLink.cs(60,0): at Interop.Kernel32.CreateSymbolicLink(String symlinkFileName, String targetFileName, Boolean isDirectory)
        /_/src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs(423,0): at System.IO.FileSystem.CreateSymbolicLink(String path, String pathToTarget, Boolean isDirectory)
        /_/src/libraries/System.Private.CoreLib/src/System/IO/File.cs(1026,0): at System.IO.File.CreateSymbolicLink(String path, String pathToTarget)
        /_/src/libraries/Microsoft.Extensions.FileProviders.Physical/tests/PhysicalFileProviderTests.netcoreapp.cs(104,0): at Microsoft.Extensions.FileProviders.PhysicalFileProviderTests.UsePollingFileWatcher_UseActivePolling_HasChanged_SymbolicLink_TargetChanged(Boolean useWildcard, Boolean linkWasBroken)
        --- End of stack trace from previous location ---

Author:	radical
Assignees:	-
Labels:	area-Extensions-FileSystem, untriaged
Milestone:	-

[adamsitnik]

cc @jozkee

[jozkee]

FWIW: I think the scenario here is: re-create a symlink with a different target i.e: delete it, then create it back.
But this error seems to be very unusual, it has been hit just once in the whole time the test has existed. Plus I tried to locally repro by doing the above mentioned 100k times in a loop and never got the error.

I will keep it in 7.0.0 since it may not be possible to fix it in 6.0.0.

cc @carlossanlop

[danmoseley]

@jozkee I don't think we should leave tests with known failure modes if possible. The failures add up. Can we either temporarily catch this exception, tracking with this issue, or disable the test, again tracking with this issue? The former seems better. LMK if you would like me to push that up.

[jozkee]

@danmoseley, I just sent #57299 for catching the exception