-
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
[release/7.0][wasm] Fix Wasm.Build.Tests with stable 7.0.0 #76939
Conversation
Tagging subscribers to this area: @directhex Issue DetailsSet the manifest package version to use ( Fixes #76908 .
|
Whenever you get a chance, can you please take a look at the CI failures? LMK when this is good to merge. |
Working on that, I'll ping you when this is ready. |
The Wasm.Build.Tests failures will be fixed by dotnet/sdk#28627 . Once, an installer with that change is available, this should be green, and can be merged. |
Set the manifest package version to use (`7.0.0` instead of `7.0.0-ci`) early. Fixes dotnet#76908 .
.. because it is not set at evaluation time. So, get it in a target, and move the WorkloadIds to a target too.
.. the import order.
There are failures showing up in the wasm legs. Are any related to this change? |
This is blocking the runtime branding PR as described here: #77549 (comment) |
@carlossanlop this is good to merge. The WasmBuildTests seem to be stuck on SIMD tests, but those are not affected by this at all. |
And once this is merged, then we can merge upstream into #77549 . |
Wasm.Build.Tests
started to fail when installing the workload manifests with #76849 which moved toStable branding for GA
. This caused the workload installation to fail because the targets were using the incorrect manifest version -7.0.0-ci
instead of7.0.0
. It is fixed here by setting that early, and using that in all the relevant places.This revealed a second issue - dotnet/sdk#28607 - which caused tests to break, and will be fixed by dotnet/sdk#28627 .
Fixes #76908 .
Customer Impact
No impact, since this is a tests-only change.
Testing
Running
Wasm.Build.Tests
.Risk
No risk, since this is a tests-only change.