dotnet/msbuild

Test `Regress314573_VeryLongPaths` fails when long paths are not enabled on Windows

Open

#10,952 建立於 2024年11月7日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)C# (5,062 star) (1,364 fork)batch import
Priority:3help wantedtriaged

描述

I set up a new machine and see a failure in Regress314573_VeryLongPaths:

Assert.Equal() Failure: Values differ
Expected: 1
Actual:   0
   at Microsoft.Build.UnitTests.ResolveAssemblyReference_Tests.Miscellaneous.Regress314573_VeryLongPaths() in S:\msbuild\src\Tasks.UnitTests\AssemblyDependency\Miscellaneous.cs:line 4919

With this in the log

ERROR MSB3248: Parameter "AssemblyFiles" has invalid value "C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\A.dll". Path: C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\A.dll exceeds the OS max path limit. The fully qualified file name must be less than 260 characters.

I think the test was trying to detect that that didn't cause a failure when it was written long long ago.

I'm not sure the current behavior is wrong though . . .

貢獻者指南

Test `Regress314573_VeryLongPaths` fails when long paths are not enabled on Windows · dotnet/msbuild#10952 | Good First Issue