Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release/7.0][wasm] System.Diagnostics.Tracing.Tests failing with chrome Expected 210 assets to be downloaded, but only finished 211 #82271

Closed
radical opened this issue Feb 16, 2023 · 6 comments
Closed

[release/7.0][wasm] System.Diagnostics.Tracing.Tests failing with chrome Expected 210 assets to be downloaded, but only finished 211 #82271

radical opened this issue Feb 16, 2023 · 6 comments
Assignees
@pavelsavara
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Milestone
7.0.x

Comments

@radical
Copy link
Member

radical commented Feb 16, 2023 •
edited by build-analysis bot
Loading

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.

cc @pavelsavara @maraf

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

Build Definition Test Pull Request
201611 dotnet/runtime Workloads-Webcil-Wasm.Build.Tests.WasmTemplateTests.WorkItemExecution
197972 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82432
197919 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82192
197634 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82851
197262 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82208
197257 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82174
197250 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82089
197231 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution
193598 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82192
192196 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82921
191057 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82174
188784 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82807
186414 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82192
182904 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82572
184113 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82089
182131 dotnet/runtime WasmTestOnBrowser-System.Diagnostics.Tracing.Tests.WorkItemExecution #82089

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 8 16
@radical radical added arch-wasm WebAssembly architecture test-failure labels Feb 16, 2023
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Feb 16, 2023
@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Feb 16, 2023
@ghost
Copy link

ghost commented Feb 16, 2023

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

Issue Details

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.

cc @pavelsavara @maraf

Author: radical
Assignees: -
Labels:

arch-wasm, test-failure
Milestone: -

@runfoapp runfoapp bot mentioned this issue Feb 16, 2023
Closed
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Feb 17, 2023
@pavelsavara pavelsavara self-assigned this Feb 17, 2023
@lewing lewing added this to the 8.0.0 milestone Feb 17, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Feb 17, 2023
@lewing lewing added untriaged New issue has not been triaged by the area owner and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Feb 17, 2023
@pavelsavara
Copy link
Member

What is msdia140.dll native file doing there ?

@pavelsavara
Copy link
Member

Larry saw it on Net7 build
So my theory I broke it last week is not valid.

This was referenced Feb 17, 2023
Merged
Merged
@pavelsavara pavelsavara mentioned this issue Feb 24, 2023
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Feb 24, 2023
@pavelsavara
Copy link
Member

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.

@buyaa-n buyaa-n mentioned this issue Mar 4, 2023
Merged
2 tasks
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Mar 8, 2023
@pavelsavara pavelsavara modified the milestones: 8.0.0, 7.0.x Mar 14, 2023
@pavelsavara pavelsavara removed the untriaged New issue has not been triaged by the area owner label Mar 14, 2023
@pavelsavara
Copy link
Member

Fixed by #82617

@ghost ghost locked as resolved and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pavelsavara pavelsavara

Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Projects
None yet
Milestone
7.0.x
Development

No branches or pull requests
4 participants
@radical @lewing @pavelsavara @jeffschwMSFT