[main] Update dependencies from dotnet/arcade

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/dotnet/arcade

• Subscription: f607b9f2-509c-4318-eb57-08d8e4d5099b
• Build: 20231018.2
• Date Produced: October 19, 2023 4:42:16 AM UTC
• Commit: 6a5ca678aef84f34a1fccc46f76623f41da56553
• Branch: refs/heads/main

• Updates:
  • Microsoft.DotNet.Arcade.Sdk: from 8.0.0-beta.23463.1 to 9.0.0-beta.23518.2

• Updates to .NET SDKs:
  • Updates sdk.version to 8.0.100-rtm.23506.1
  • Updates tools.dotnet to 8.0.100-rtm.23506.1

[RussKie]

test\UnitTests\UnitTests.csproj(0,0): error NU1202: (NETCORE_ENGINEERING_TELEMETRY=Restore) Package xunit.runner.visualstudio 2.5.1 is not compatible with net452 (.NETFramework,Version=v4.5.2). Package xunit.runner.visualstudio 2.5.1 supports:
  - net462 (.NETFramework,Version=v4.6.2)
  - net6.0 (.NETCoreApp,Version=v6.0)

This looks related to dotnet/arcade#14036. @ViktorHofer any thoughts on how to fix this?

[RussKie]

@ajcvickers can someone from your team look into this too?

[ViktorHofer]

This looks related to dotnet/arcade#14036. @ViktorHofer any thoughts on how to fix this?

xunit.runner.visualstudio/2.5.1 doesn't support EOL runtimes anymore: https://www.nuget.org/packages/xunit.runner.visualstudio/2.5.1#dependencies-body-tab. .NET Framework 4.5.2 has been out of support for years. Can you update that TFM to the minimum in support version which is net462?

[mgravell]

to help unblock this, I have proposed (since I was on build-ops): #2162 - let's see how happy/unhappy CI is with that - then we can combine these?

[amcasey]

Test failure looks like a change in the formatting of test assert failure messages

                                  ↓ (pos 22)
Expected: ···"sert.Equal() Failure\r\nExpected: 5\r\nActual"···
Actual:   ···"sert.Equal() Failure: Values differ\r\nExpe"···
                                  ↑ (pos 22)

[ErikEJ]

@amcasey I just did a PR attempt to fix this: #2163

[amcasey]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).