-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[8.0] [wasm] Expected the multithreading runtime pack to be available when running on CI. IsRunningOnCI is true but IsWorkloadWithMultiThreadingForDefaultFramework is false #90805
Labels
arch-wasm
WebAssembly architecture
area-Build-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
os-linux
Linux OS (any supported distro)
os-windows
Milestone
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError Blob{
"ErrorMessage": "Expected the multithreading runtime pack to be available when running on CI. IsRunningOnCI is true but IsWorkloadWithMultiThreadingForDefaultFramework is false",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": true
} Reproduction Steps
|
Duplicate of #90742 , and fixed yesterday. The build linked here is older. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly architecture
area-Build-mono
Known Build Error
Use this to report build issues in the .NET Helix tab
os-linux
Linux OS (any supported distro)
os-windows
Error Blob
Reproduction Steps
-msimd128
#90750browser-wasm linux Release WasmBuildTests
browser-wasm windows Release WasmBuildTests
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=377484
Error message validated:
Expected the multithreading runtime pack to be available when running on CI. IsRunningOnCI is true but IsWorkloadWithMultiThreadingForDefaultFramework is false
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/18/2023 3:59:22 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: