Branch-merge bot does not work on aspnetcore-tooling due to files that exceed MAX_PATH

[natemcmaster]

The bot that merges release/* branches back to master does not work on https://github.com/aspnet/AspNetCore-Tooling because this repo contains files which exceed MAX_PATH.

error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_EventCallback_SpecifiesValueAndExpression_Generic/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_EventCallback_SpecifiesValue_WithMatchingProperties/TestComponent.codegen.cs: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_EventCallback_SpecifiesValue_WithMatchingProperties/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithMatchingProperties/TestComponent.codegen.cs: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithMatchingProperties/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithoutMatchingProperties/TestComponent.codegen.cs: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithoutMatchingProperties/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/ChildComponent_WithGenericChildContent_SetsParameterNameOnComponent/TestComponent.codegen.cs: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/ChildComponent_WithGenericChildContent_SetsParameterNameOnComponent/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentDesignTimeCodeGenerationTest/EventHandler_OnElement_ArbitraryEventName_WithEventArgsMethodGroup/TestComponent.mappings.txt: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentRuntimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithoutMatchingProperties/TestComponent.codegen.cs: Filename too long
error: unable to create file src/Razor/test/Microsoft.AspNetCore.Razor.Language.Test/TestFiles/IntegrationTests/ComponentRuntimeCodeGenerationTest/BindToComponent_SpecifiesValueAndChangeEvent_WithoutMatchingProperties/TestComponent.mappings.txt: Filename too long

https://dev.azure.com/dnceng/internal/_build/results?buildId=104473

cc @dougbu @rynowak

[HaoK]

Note this is also blocking these test files from being used on helix

[dougbu]

72b939d85573

[HaoK]

@dougbu this max path issue also exists for https://github.com/aspnet/AspNetCore/tree/master/src/Mvc/Mvc.Api.Analyzers/test/TestFiles and https://github.com/aspnet/AspNetCore/tree/master/src/Mvc/Mvc.Analyzers/test/TestFiles which causes helix to reject these work items since the combined path is too long, do you think you can apply the same fix to those as well?

[dougbu]

@HaoK if there's an issue, I can take it. Just assign it to me.

But, we shouldn't try to reuse this issue because it was about a related issue in the AspNetCore-Tooling repo.