[browser] Use StaticWebAssets fingerprinting in Wasm SDK #103755
Build #20240722.184 had test failures
Details
- Failed: 4 (0.00%)
- Passed: 3,103,992 (97.95%)
- Other: 64,873 (2.05%)
- Total: 3,168,869
Annotations
Check failure on line 19 in .dotnet\sdk\9.0.100-preview.5.24307.3\NuGet.RestoreEx.targets
azure-pipelines / runtime
.dotnet\sdk\9.0.100-preview.5.24307.3\NuGet.RestoreEx.targets#L19
.dotnet\sdk\9.0.100-preview.5.24307.3\NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) Static graph-based restore failed with exit code '1' but did not log an error. Please file an issue at https://github.com/NuGet/Home.
Check failure on line 337 in src\mono\mono.proj
azure-pipelines / runtime
src\mono\mono.proj#L337
src\mono\mono.proj(337,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command "powershell -NonInteractive -command "& D:\a\_work\1\s\src\mono\wasi\\provision.ps1 -WasiSdkUrl https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-22/wasi-sdk-22.0.m-mingw64.tar.gz -WasiSdkVersion 22 -WasiSdkPath D:/a/_work/1/s/src/mono/wasi/wasi-sdk/ -WasiLocalPath D:\a\_work\1\s\src\mono\wasi\; Exit $LastExitCode "" exited with code 1.
azure-pipelines / runtime
.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24360.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91
.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24360.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-ST-System.Runtime.Tests in job b663a7a9-9f88-4b94-b9b8-9575525802d1 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/b663a7a9-9f88-4b94-b9b8-9575525802d1/workitems/WasmTestOnChrome-ST-System.Runtime.Tests/console
azure-pipelines / runtime
.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91
.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.IO.FileSystem.Tests in job f319850d-3b56-41a7-9951-5124e3ee6f5c has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/f319850d-3b56-41a7-9951-5124e3ee6f5c/workitems/WasmTestOnChrome-MT-System.IO.FileSystem.Tests/console
Check failure on line 1 in WasmTestOnV8-ST-System.Runtime.Tests.WorkItemExecution
azure-pipelines / runtime
WasmTestOnV8-ST-System.Runtime.Tests.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in System.Tests.UriCreateStringTests.Path_Query_Fragment
azure-pipelines / runtime
System.Tests.UriCreateStringTests.Path_Query_Fragment
Test failed
Check failure on line 1 in WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution
azure-pipelines / runtime
WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
azure-pipelines / runtime
WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.