-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[workload] Fix the SDK band version and base the WBT on the sdk flow #107899
Conversation
hmm I'm not sure this works without some of the other changes from the NET10 PR |
It doesn't work with them either, I was trying to illustrate the problem in dotnet/sdk#43070 to @marcpopMSFT |
Just to make it more clear the SDK band version we're constructing right now in main is We might be able to reenable the multiple band logic and produce a |
Why can't you make it |
Trying again with a recent 10.0.100 sdk |
@marcpopMSFT current failure is that the alpha.2 SDK only has workload sets which breaks our test setup |
It has workload sets? You mean the baseline workload set is breaking the test setup somehow? CC @dsplaisted if that's the case to see if he has ideas on how we reversion in the workload set world. |
So far it was just expecting a directory that wasn't there. Hopefully I was just overly pessimistic, will see if I can get it working here. |
Any luck? What folder? Do we have an option of having wasm workloads broken for a short time in sdk so we can get the rest of the repo and net10 work working? |
I had to flow some updates from emsdk which is not fast (see dotnet/dnceng#4111 ) but I'm trying again now |
too late to change it? if it's going to be a continuous pain, perhaps take a hit now? |
<!-- Required for running apps built with 9.0 sdk, but the sdk does | ||
not yet support *running* with 9.0 sdk --> | ||
<AdditionalSharedFrameworkToInstallArguments Include="-Version latest -Channel 8.0 -Quality daily" /> | ||
<!-- Required for running apps built with 10.0 sdk, but the sdk does |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in this file look good.
if (!Directory.Exists(outputDir)) | ||
{ | ||
Log.LogMessage($"Could not find {name} directory at {outputDir}. Creating it.."); | ||
Directory.CreateDirectory(outputDir); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in this file look good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The workload task+installation specific changes LGTM 👍
I've merged what was remaining of this into #106599 which is farther along now |
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
No description provided.