`System.IO.Tests.DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException` test failing

[radical]

Build, and Log

    System.IO.Tests.DirectoryInfo_Create.DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException [FAIL]
      Assert.All() Failure: 2 out of 2 items in the collection did not pass.
      [1]: Item: \\?\C:\h\w\BFA20AC3\t\DirectoryInfo_Create_ipbli234.zri\DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException_271_a66fa5a7\802869a5d16b495fa5d074e146cb2cd7...

Xunit.Sdk.XunitException: Expected one of: (System.IO.PathTooLongException, System.IO.DirectoryNotFoundException) -> Actual: (System.IO.IOException)
              at System.AssertExtensions.ThrowsAnyInternal(Action action, Type[] exceptionTypes) in /_/src/libraries/Common/tests/TestUtilities/System/AssertExtensions.cs:line 212
              at System.AssertExtensions.ThrowsAny[TFirstExceptionType,TSecondExceptionType](Action action) in /_/src/libraries/Common/tests/TestUtilities/System/AssertExtensions.cs:line 222
              at System.IO.Tests.Directory_CreateDirectory.<DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException>b__27_0(String path) in /_/src/libraries/System.IO.FileSystem/tests/Directory/CreateDirectory.cs:line 274
              at Xunit.Assert.All[T](IEnumerable`1 collection, Action`1 action) in /_/src/xunit.assert/Asserts/CollectionAsserts.cs:line 36

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Build, and Log

    System.IO.Tests.DirectoryInfo_Create.DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException [FAIL]
      Assert.All() Failure: 2 out of 2 items in the collection did not pass.
      [1]: Item: \\?\C:\h\w\BFA20AC3\t\DirectoryInfo_Create_ipbli234.zri\DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException_271_a66fa5a7\802869a5d16b495fa5d074e146cb2cd7...

Xunit.Sdk.XunitException: Expected one of: (System.IO.PathTooLongException, System.IO.DirectoryNotFoundException) -> Actual: (System.IO.IOException)
              at System.AssertExtensions.ThrowsAnyInternal(Action action, Type[] exceptionTypes) in /_/src/libraries/Common/tests/TestUtilities/System/AssertExtensions.cs:line 212
              at System.AssertExtensions.ThrowsAny[TFirstExceptionType,TSecondExceptionType](Action action) in /_/src/libraries/Common/tests/TestUtilities/System/AssertExtensions.cs:line 222
              at System.IO.Tests.Directory_CreateDirectory.<DirectoryLongerThanMaxLongPathWithExtendedSyntax_ThrowsException>b__27_0(String path) in /_/src/libraries/System.IO.FileSystem/tests/Directory/CreateDirectory.cs:line 274
              at Xunit.Assert.All[T](IEnumerable`1 collection, Action`1 action) in /_/src/xunit.assert/Asserts/CollectionAsserts.cs:line 36

Author:	radical
Assignees:	-
Labels:	area-System.IO, untriaged
Milestone:	-

[danmoseley]

I just hit this too https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-64008-merge-e31c2ef07eb04bed87/System.IO.FileSystem.Tests/1/console.8fa36a2b.log?sv=2019-07-07&se=2022-02-08T18%3A27%3A22Z&sr=c&sp=rl&sig=9NCp1RxSJuCn0PIOUSr31uYMCVsCgRTA2nngbCPnNxI%3D
#63824
The machine names are different though (first line). Perhaps some other IO test is leaving a mess? It's too bad we can' see the exception message.

[danmoseley]

@dotnet/dnceng did something change with the "windows.11.amd64.clientpre.open" queue at about 2022-01-19 17:36:32.7150000 ? This test never failed before then, then consistently failed after that.

[MattGal]

@{Matt's team} did something change with the "windows.11.amd64.clientpre.open" queue at about 2022-01-19 17:36:32.7150000 ? This test never failed before then, then consistently failed after that.

I'll take this one, since I'm working in this space right now (also feel free to hit me up on Teams to discuss further)

Yes and no :) The image used in that queue hasn't changed since December (I can tell this because image version is still 2021.1220.204422). However, this corresponds to when we allowed Azure Security Pack to start doing its thing (this is an S360 requirement) to prevent the angry "missing AzSecPack" issues from popping up.

If there's something you can identify (ideally using a DTL VM) what you consider wrong here, we can talk about how to work around it, but unfortunately opting out of AzSecPack is not an option unless we make Helix machines automatically get deleted every 4 hours.

[danmoseley]

Hi @MattGal it would be interesting to know what error message this code produces on the machine: https://gist.github.com/danmoseley/9ba23a2455a3f28e67bf57d7ca9b2838
and also whether long paths are enabled

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd#enable-long-paths-in-windows-10-version-1607-and-later