-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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-testing] Add properties for nuget.config path, and target t… #99277
Conversation
Tagging subscribers to this area: @directhex Issue Details…o run the main target after
|
@ilonatommy Would you please mind checking this does not break installing the sdk+workload for local runs? |
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 look good to me 👍
src/mono/nuget/Microsoft.NET.Runtime.WorkloadTesting.Internal/Sdk/WorkloadTesting.Core.targets
Outdated
Show resolved
Hide resolved
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.
artifacts/dotnet-latest
has wasm-experimental, wasm-tools, wasm-tools-net8, wasm-experimental-net8
.
.dotnet
has 0 workloads.
This is the expected state, wbt pass locally.
src/mono/nuget/Microsoft.NET.Runtime.WorkloadTesting.Internal/Sdk/WorkloadTesting.Core.targets
Outdated
Show resolved
Hide resolved
Thanks for the review! And @ilonatommy thank you for checking the local build! |
@jkotas thanks for the merge! |
src/mono/nuget/Microsoft.NET.Runtime.WorkloadTesting.Internal/Sdk/WorkloadTesting.Core.targets
Outdated
Show resolved
Hide resolved
This looks like unrelated commits got pulled into it |
…o run the main target after
…Sdk/WorkloadTesting.Core.targets Co-authored-by: Marek Fišera <[email protected]>
…Sdk/WorkloadTesting.Core.targets
…Sdk/WorkloadTesting.Core.targets
d217e70
to
f0ad282
Compare
I had merged main which fixed the diff, but the list of commits still includes extra ones. I have rebased the changes on |
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
Failures are known issues. |
…o run the main target after