[release/7.0] Update dependencies from dotnet/xharness

[dotnet-maestro]

This pull request updates the following dependencies

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

• Subscription: 6b81852c-1721-4f1f-0dc3-08db2b057d40
• Build: 20230313.1
• Date Produced: March 13, 2023 6:05:54 PM UTC
• Commit: 0ff1a841e0a5949428c3868258b14ddcfa0da903
• Branch: refs/heads/main

• Updates:
  • Microsoft.DotNet.XHarness.CLI: from 1.0.0-prerelease.22411.1 to 1.0.0-prerelease.23163.1
  • Microsoft.DotNet.XHarness.TestRunners.Common: from 1.0.0-prerelease.22411.1 to 1.0.0-prerelease.23163.1
  • Microsoft.DotNet.XHarness.TestRunners.Xunit: from 1.0.0-prerelease.22411.1 to 1.0.0-prerelease.23163.1

[carlossanlop]

@lewing or @steveisok - Would you mind helping with the merge conflict?

     <add key="darc-pub-dotnet-emsdk-7fa7119" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-emsdk-7fa7119c/nuget/v3/index.json" />

[steveisok]

@lewing or @steveisok - Would you mind helping with the merge conflict?

     <add key="darc-pub-dotnet-emsdk-7fa7119" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-emsdk-7fa7119c/nuget/v3/index.json" />

Done!

[carlossanlop]

@steveisok @lewing There's a failure that seems related to this PR. It's affecting mainly wasm linux queues, but also MacCatalyst.

The two key error messages are:

• "You must install or update .NET to run this application."
• "xharness-event-processor.py': [Errno 2] No such file or directory"

Affected queues:

• Build Browser wasm Linux Release LibraryTests
• Build Browser wasm Linux Release LibraryTests_EAT
• Build Browser wasm Linux Release LibraryTests_AOT
• Build MacCatalyst x64 Release AllSubsets_Mono

Job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=220477&view=logs&j=11c5c840-d20a-5536-428b-70d8cd9c6259&t=73598586-463f-5241-5dc8-b8ffdebf8b89&l=81

Log file: https://helixre107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-pull-83828-merge-636cccecbebd482fad/WasmTestOnBrowser-Common.Tests/1/console.e9cfdcba.log?helixlogtype=result

Full error message:

===========================================================================================================
/datadisks/disk1/work/C18709D2/w/9B8E0882/e /datadisks/disk1/work/C18709D2/w/9B8E0882/e /datadisks/disk1/work/C18709D2/w/9B8E0882/e
You must install or update .NET to run this application.

App: /datadisks/disk1/work/C18709D2/p/microsoft.dotnet.xharness.cli/1.0.0-prerelease.23163.1/tools/net7.0/any/Microsoft.DotNet.XHarness.CLI.dll
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '7.0.0' (x64)
.NET location: /datadisks/disk1/work/C18709D2/p/dotnet-cli/

The following frameworks were found:
  7.0.0-rc.2.22472.3 at [/datadisks/disk1/work/C18709D2/p/dotnet-cli/shared/Microsoft.NETCore.App]

Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=7.0.0&arch=x64&rid=ubuntu.18.04-x64
/datadisks/disk1/work/C18709D2/w/9B8E0882/e /datadisks/disk1/work/C18709D2/w/9B8E0882/e
----- end Wed Mar 29 01:32:28 UTC 2023 ----- exit code 150 ----------------------------------------------------------
XHarness artifacts: /datadisks/disk1/work/C18709D2/w/9B8E0882/uploads/xharness-output
+ export _commandExitCode=150
+ /usr/bin/python3 -u /datadisks/disk1/work/C18709D2/w/9B8E0882/u/xharness-event-processor.py
/usr/bin/python3: can't open file '/datadisks/disk1/work/C18709D2/w/9B8E0882/u/xharness-event-processor.py': [Errno 2] No such file or directory

[steveisok]

@akoeplinger where does arcade pick up what sdk version to install?

[carlossanlop]

Reminder: Code complete is on April 10th to ensure this change gets included in the May Servicing Release.

[akoeplinger]

where does arcade pick up what sdk version to install?

From here if I remember correctly https://github.com/dotnet/arcade/blob/d7b5c2c026141e80abf3acca2f957c52949929cc/src/Microsoft.DotNet.Helix/Sdk/tools/dotnet-cli/DotNetCli.props#L6

But I think we should wait for the xharness branch: dotnet/xharness#1010

[carlossanlop]

Per the conversation in the 6.0 xharness dependency flow PR, I have disabled runtime's darc subscriptions to xharness in 6.0 and 7.0, and we can close the PRs.