Update Microsoft.DotNet.Helix.Sdk

[akoeplinger]

Extracted from #67771 to get the fix for #67349

Updates the WASM tests to always use net6.0 until we can upgrade to a net7.0 SDK.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[premun]

Yeah, this should work

[akoeplinger]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Extracted from #67771 to get the fix for #67349

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[steveisok]

@akoeplinger @premun Is there something wrong with the xharness bump?

I'm seeing this in some of the failed runs:

/usr/bin/python3 -u /datadisks/disk1/work/BF180A16/w/A18D0948/u/xharness-event-processor.py
/usr/bin/python3: can't open file '/datadisks/disk1/work/BF180A16/w/A18D0948/u/xharness-event-processor.py': [Errno 2] No such file or directory

[akoeplinger]

There is an issue on the wasm DebuggerTests leg that blocks this yeah

[premun]

Ignore the Python error, that one is normal for all wasm runs even though they were supposed to turn off the telemetry to hide it. Regardless it is harmless

[steveisok]

Are you sure? Some of these legs have all passes in their testResults.xml, but yet are being flagged as a failure.

[premun]

@steveisok can you show me an example?

[akoeplinger]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[premun]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[premun]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[premun]

@akoeplinger the build is looking good so far. I believe it's going to finish green.

The one failing wasm leg is a failing test, I checked the logs

[akoeplinger]

@premun not sure whether the two failing wasm jobs are real failures, they just print this which is weird:

Console log: 'normal-Invariant.Tests' from job 1a207a32-525d-408a-9972-8eb73eaf1dd3 (windows.amd64.server2022.open) using docker image mcr.microsoft.com/dotnet-buildtools/prereqs:windowsservercore-ltsc2022-helix-webassembly-20220317203903-1ad56e8 on a002BY9
running %HELIX_CORRELATION_PAYLOAD%\scripts\2e67926377ad48d28d153418c420f78b\execute.cmd in C:\h\w\A091093F\w\9EB708DD\e max 3600 seconds

Output:

Exit Code:-900

[premun]

@radical do you know what could be up with the two failing WASM legs? We are forcing .NET 6.0 SDK in this PR like I was describing

[akoeplinger]

@premun I just looked at the run_py.log and it looks like an infrastructure issue with Docker to me:

2022-04-20T16:11:48.431Z	ERROR  	dockerhelper(234)	run	API Error attempting to talk to Docker Server:500 Server Error: Internal Server Error ("CreateComputeSystem b470dbaa253592a57acb6c7ff8844c3d06337e4a756be9d52be9b942f7fd80a0: The request is not supported.
(extra info: 

[akoeplinger]

Yay, it's green ✅ 🎉

@premun thank you for digging into this!