Wasi provisioning failing

[lewing]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=750876
Build error leg or test failing: Build / wasi-wasm windows Release LibraryTests_Smoke / Build product
Pull request: #105277

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["The command", "provision.ps1"],
  "ErrorPattern": "",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=750876
Error message validated: [The command provision.ps1]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2024 1:29:25 AM UTC

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

[lewing]

cc @dicej

[pavelsavara]

The underlying issue is truncated gzip input.
I think it means that the download was not complete.

We could upgrade to WASI SDK 23 now
https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-23

And then update the CI agent images to contain it.

[dicej]

Is this still an issue? It looks like the linked PR was merged, so maybe it was a spurious network failure?

[pavelsavara]

I think I fixed it with $ProgressPreference = 'SilentlyContinue' in #105321

I'm leaving this open to observe the CI for few more days

[lewing]

still failing but possibly less often

[pavelsavara]

We don't have way how to fix it until we switch to our own nuget ...