Skip to content

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

Closed

Description

@radical

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

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Feb 16, 2023
  2. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Feb 16, 2023
  3. ghost added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Feb 17, 2023
  4. self-assigned this
    on Feb 17, 2023
  5. added this to the 8.0.0 milestone on Feb 17, 2023
  6. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on Feb 17, 2023
  7. added
    untriagedNew issue has not been triaged by the area owner
    and removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Feb 17, 2023
  8. pavelsavara commented on Feb 17, 2023

    @pavelsavara
    Member

    What is msdia140.dll native file doing there ?

  9. pavelsavara commented on Feb 17, 2023

    @pavelsavara
    Member

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

  10. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 24, 2023
  11. pavelsavara commented on Feb 24, 2023

    @pavelsavara
    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.

  12. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Mar 8, 2023
  13. modified the milestones: 8.0.0, 7.0.x on Mar 14, 2023
  14. removed
    untriagedNew issue has not been triaged by the area owner
    on Mar 14, 2023
  15. pavelsavara commented on Mar 14, 2023

    @pavelsavara
    Member

    Fixed by #82617

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions