-
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
[6.0] WASM CI failure: WorkloadManifestCompositionException: Workload manifest dependency 'Emscripten' version '6.0.4' is lower than version '6.0.13' required by manifest 'mono.toolchain' #80574
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFound in 6.0 PR: #80554 Queue:
|
Not sure if also related, but in the log I see this additional build failure that is not showing up as the main error:
|
looks likr the 6.0.400 sdk branch has very stale baseline manifests (well behind the 6.0.1xx branch) but I'm not sure that is the cause |
this could be the flow issue, a new emsdk build and version should be incoming soon, lets see if that gets the correct stable darc branch in the flow |
|
I mainly noticed that the emscripten version in release/6.0-1xx (6.0.13) was newer than release/6.0-4xx (6.0.4) which does seem wrong? especially since 6.0.x is using a manifest that is blacklisted now? |
That's because there's a CoherentParentDependency in 6.0.1xx so it gets updated whenever runtime updates. It probably shouldn't. Let's talk in the sync in two weeks. |
why is https://www.nuget.org/packages/Microsoft.NET.Workload.Emscripten.Manifest-6.0.400 on nuget.org but not in the dotnet6 feed? |
@carlossanlop #80591 will bump the version for 6.0.x and hopefully end up in the feed |
Merged. |
Found in 6.0 PR: #80554
Queue:
Build Browser wasm Release AllSubsets_Mono_WasmBuildTests
Step: Build product
Job result: https://dev.azure.com/dnceng-public/public/_build/results?buildId=135390&view=logs&j=3a9f831a-39fc-5a98-005d-1222ec2c60ca&t=43ac2bf6-9cb4-5da7-8a9d-b264068ff198&l=3667
Full error message:
The text was updated successfully, but these errors were encountered: