Closed ericstj closed 9 months ago
I noticed that we might not get dotnet
added to the path:
https://github.com/dotnet/arcade/blob/c0c425d9b85b125bbaf59581639355f1d2b99149/src/Microsoft.DotNet.Helix/Sdk/tools/dotnet-cli/DotNetCli.targets#L15
So we might need to tweak our command line for executing the tests: https://github.com/dotnet/machinelearning/blob/5483ba93c591367e9465884ca23feab79f4bf1f0/eng/helix.proj#L151
Yep, right on time as I discovered this the tests hit it. I do see this is having the desired effect (runtime added, but no SDK): https://helixde107v0xdeko0k025g8.blob.core.windows.net/helix-job-f33c5c7d-ade1-462f-bbf7-9c7eceea97510e66aa157474e3aad/job-list-92e85b36-8b0e-416c-b245-155dc7a13ad0.json?helixlogtype=result
Now to get dotnet
back on the path.
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
efab011
) 68.79% compared to head (51a7461
) 68.79%. Report is 1 commits behind head on main.
I noticed that the tests included the latest SDK - including the host - in our helix payloads.
This is a large amount of unnecessary downloads and it also makes it so we use the latest host on the older frameworks which can fail when the latest host drops support for distros.
Since our tests shouldn't need the full CLI, remove this from our helix payloads.
We'll instead get just the runtime we need through
AdditionalDotNetPackage