-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use aspnetcore runtime
only instead of full SDK to run XHarness
#7787
Comments
I think this is another side effect of using an unreleased version of the sdk. I'm not sure there's a good way to see which runtimes are supposed to go with nightly unreleased versions. Once RC1 actually releases we need to move all repos to use the released version instead of the one we took to unblock nuget restores. |
Cool, so let's do it then. Should I put this todo next to the |
Is there a reason why it's not desirable to just always install the SDK? It seems like it's actually a goal for us to be able to use daily sdks in repos. |
I just assumed we save bandwidth since we need the runtime only. But if it doesn't matter much, I don't care which one we use. |
* Use full .NET SDK to run XHarness (temporarily) #7787 * Add TODOs, lock the RC1 version better
This is waiting for Arcade to switch onto .NET 7 preview 1 |
Context
To run XHarness through Helix SDK, we need ASP.NET runtime. However, in .NET 6 RC 1 the versions of the bundled NETCore.App runtime are somehow lower and the NETCore.App that is bundled with ASP.NET runtime cannot run XHarness CLI.
The version and type of .NET is set here:
https://github.com/dotnet/arcade/blob/main/src/Microsoft.DotNet.Helix/Sdk/tools/xharness-runner/XHarnessRunner.targets#L6
For this reason, we switched to using the full SDK in the XHarness workloads which is probably unnecessary in the future.
Problem details
.NET says it cannot find a runtime but the runtime seems to be present:
1) Installing aspnetcore runtime only
2) Installing dotnet runtime only
3) Installing both dotnet+aspnetcore runtimes
Finally worked
Goal
As a workaround, we switched to using the full SDK in the XHarness workloads. Once we are past RC1 - maybe RC2, maybe full .NET 6 - start using the
aspnetcore runtime
only to run XHarness (basically revert the last change).The text was updated successfully, but these errors were encountered: