Fix WASM boot config ContentRoot to use IntermediateOutputPath#124125
Merged
Build Analysis / Build Analysis
failed
Mar 2, 2026 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
🕒 The following pipeline(s) will be analyzed once they finish
Known Repository Errors
Build Failures
runtime / Build / browser-wasm linux Release CoreCLR / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/tasks/Microsoft.NET.Sdk.WebAssembly.Pack.Tasks/ComputeWasmPublishAssets.cs(626,77): error CS0103: The name 'isWebCilEnabled' does not exist in the current context
runtime / Build / browser-wasm windows Release CoreCLR / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src\tasks\Microsoft.NET.Sdk.WebAssembly.Pack.Tasks\ComputeWasmPublishAssets.cs(626,77): error CS0103: The name 'isWebCilEnabled' does not exist in the current context
runtime / Build / browser-wasm linux Release LibraryTests / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/tasks/Microsoft.NET.Sdk.WebAssembly.Pack.Tasks/ComputeWasmPublishAssets.cs(626,77): error CS0103: The name 'isWebCilEnabled' does not exist in the current context
11 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime] [dotnet-linker-tests]
Was this helpful?
Loading