dotnet / dotnet/msbuild

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

Open
#10,952 1 comment 0 reactions 0 assignees View on GitHub
help wanted Priority:3 triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 8h
Merged PRs (30d)
141

Description

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 . . .

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.