Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Regression: Workload ID wasm-tools is not recognized. #26967

Closed
radical opened this issue Aug 3, 2022 · 5 comments
Closed

Regression: Workload ID wasm-tools is not recognized. #26967

radical opened this issue Aug 3, 2022 · 5 comments
Labels
Area-Workloads untriaged Request triage from a team member

Comments

@radical
Copy link
Member

radical commented Aug 3, 2022 •
edited by thaystg
Loading

With installer version 7.0.100-rc.1.22403.4, installing the wasm-tools workload fails with:

 $ ./dotnet workload install wasm-tools -v diag
Workload ID wasm-tools is not recognized.

IIUC, this corresponds to dotnet/installer@6996a553 .
The previous version - 7.0.100-rc.1.22403.4 ( dotnet/installer@a7f1b1c5) works fine.

There was only commit in from good to bad (dotnet/installer@a7f1b1c...6996a55) - update dependencies from dotnet/sdk). And the corresponding sdk side changes: 80e6952...a121b7a .

It lists the workloads though:

 $ ./dotnet workload search

Workload ID            Description
---------------------------------------------------------------------------
android                .NET SDK Workload for building Android applications.
android-33             Preview support for Android API-33.
macos                  .NET SDK Workload for building macOS applications.
maui-android           .NET MAUI SDK for Android
maui-tizen             .NET MAUI SDK for Tizen
maui-windows           .NET MAUI SDK for Windows
runtimes-windows       workloads/runtimes-windows/description
wasm-experimental      workloads/wasm-experimental/description
wasm-tools             .NET WebAssembly build tools

This is breaking runtime CI also.

cc @lewing
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Workloads untriaged Request triage from a team member labels Aug 3, 2022
@radical
Copy link
Member Author

radical commented Aug 3, 2022

cc @steveisok I think this affects mobile workloads also.

 $ ./dotnet workload install macos
Workload ID macos is not recognized.
vscode@ [ /tmp/dbad ]
 $ ./dotnet workload install android
Workload ID android is not recognized.

@radical radical mentioned this issue Aug 3, 2022
Closed
@radical
Copy link
Member Author

radical commented Aug 3, 2022

cc @gkulin @marcpopMSFT

@marcpopMSFT
Copy link
Member

Repros with the zip install, doesn't repro in the dogfood environment. Probably caused by this codeflow but this isn't broken in 6.0.400: https://github.com/dotnet/sdk/pull/26796/files. Maybe it doesn't work with a change in main or something off in the merge?

@marcpopMSFT
Copy link
Member

Daniel's fix to 6.0.400 should fix this so I merged the auto-flow to main: #26971. Should be fixed once that gets into installer.

@radical
Copy link
Member Author

radical commented Aug 5, 2022

The flow PR has merged - dotnet/installer#14258 . And the latest build is working. thank you!

@radical radical closed this as completed Aug 5, 2022
radical added a commit to radical/runtime that referenced this issue Aug 5, 2022
@radical
Wasm.Build.Tests: re-enable building with latest sdk
af64a00 
The sdk issue dotnet/sdk#26967 was fixed in
dotnet/sdk#26796 .

Fixes dotnet#73312 .
@radical radical mentioned this issue Aug 5, 2022
Merged
radical added a commit to dotnet/runtime that referenced this issue Aug 5, 2022
@radical
Wasm.Build.Tests: re-enable building with latest sdk (#73423)
dafc6df 
The sdk issue dotnet/sdk#26967 was fixed in
dotnet/sdk#26796 .

Fixes #73312 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Workloads untriaged Request triage from a team member
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@radical @marcpopMSFT