Repository navigation
[release/7.0][wasm] System.Diagnostics.Tracing.Tests failing with chrome Expected 210 assets to be downloaded, but only finished 211 #82271
Copy link
Copy link
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-VM-meta-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'test-failure
Milestone
Description
Rolling build, and log:
[02:30:15] info: browser: [main] Console websocket connected.
[02:30:18] fail: [out of order message from the browser]: http://127.0.0.1:49254/managed/msdia140.dll - Failed to load resource: net::ERR_CACHE_READ_FAILURE
[02:30:27] fail: [out of order message from the browser]: http://127.0.0.1:49254/dotnet.js 4:47754 Uncaught Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
[02:30:27] fail: [out of order message from the browser]: http://127.0.0.1:49254/dotnet.js 4:47754 Uncaught Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
[02:30:27] fail: [out of order message from the browser]: http://127.0.0.1:49254/test-main.js 342:0 Uncaught Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
[02:30:27] fail: MONO_WASM: onRuntimeInitializedAsync() failed: {}
[02:30:27] fail: MONO_WASM: Stacktrace:
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] fail: Error: Assert failed: Expected 210 assets to be downloaded, but only finished 211
at us (http://127.0.0.1:49254/dotnet.js:5:47755)
at async hc (http://127.0.0.1:49254/dotnet.js:5:96851)
[02:30:27] info: WASM EXIT 1
Hit on PRs too.
Known Issue Error Message
Fill the error message using known issues guidance.
{
"ErrorPattern": ".*Error: Assert failed.*Expected.*assets to be downloaded, but only finished.*",
"BuildRetry": false
}Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 8 | 16 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-VM-meta-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'test-failure
Activity
pavelsavara commentedon Feb 17, 2023
What is
msdia140.dllnative file doing there ?pavelsavara commentedon Feb 17, 2023
Larry saw it on Net7 build
So my theory I broke it last week is not valid.
pavelsavara commentedon Feb 24, 2023
So, this is caused by counting download retry multiple times, only when the download fails during
await response.arrayBuffer()but after HTTP headers are already fetched.pavelsavara commentedon Mar 14, 2023
Fixed by #82617