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.

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

[wasm][wbt] Wasm.Build.Tests.WasmBuildAppTest.TopLevelMain failed #72880

Closed
pavelsavara opened this issue Jul 26, 2022 · 3 comments · Fixed by #72983
Closed

[wasm][wbt] Wasm.Build.Tests.WasmBuildAppTest.TopLevelMain failed #72880

pavelsavara opened this issue Jul 26, 2022 · 3 comments · Fixed by #72983
Assignees
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Milestone

Comments

@pavelsavara
Copy link
Member

Wasm.Build.Tests.WasmBuildAppTest.TopLevelMain(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = True, ProjectFileContents = placeholder, ExtraBuildArgs =  }, host: V8, id

        [wasm test] [16:59:27] info: console.debug: [MONO] AOT: FOUND method System.Runtime.Loader.AssemblyLoadContext:OnProcessExit () [0x181a - 0x181b 0x55dd8]
        [wasm test] [17:14:27] fail: Tests timed out after 900secs
        [wasm test] [17:14:27] info: Process 1908 didn't exit within 00:15:00 and will be killed
        [wasm test] 
        [wasm test] [17:14:27] dbug: Saving diagnostics data to 'C:\helix\work\workitem\e\diagnostics.json'
        [wasm test] [17:14:27] info: Killing process tree of 1908...
        [wasm test] 
        [wasm test] [17:14:27] info: Pids to kill: 1908
        [wasm test] 
        [wasm test] [17:14:27] info: Running lldb diagnostics for pid 1908
        [wasm test] 
        [wasm test] [17:14:27] info: Printing backtrace for pid=1908
        [wasm test] 
        [wasm test] [17:14:27] info: lldb was not found, skipping diagnosis..
        [wasm test] 
        [wasm test] XHarness exit code: 70 (TIMED_OUT)
        Exit code: 70

@pavelsavara pavelsavara added arch-wasm WebAssembly architecture test-failure labels Jul 26, 2022
@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
Copy link

ghost commented Jul 26, 2022

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

Issue Details
Wasm.Build.Tests.WasmBuildAppTest.TopLevelMain(buildArgs: BuildArgs { ProjectName = placeholder, Config = Release, AOT = True, ProjectFileContents = placeholder, ExtraBuildArgs =  }, host: V8, id

        [wasm test] [16:59:27] info: console.debug: [MONO] AOT: FOUND method System.Runtime.Loader.AssemblyLoadContext:OnProcessExit () [0x181a - 0x181b 0x55dd8]
        [wasm test] [17:14:27] fail: Tests timed out after 900secs
        [wasm test] [17:14:27] info: Process 1908 didn't exit within 00:15:00 and will be killed
        [wasm test] 
        [wasm test] [17:14:27] dbug: Saving diagnostics data to 'C:\helix\work\workitem\e\diagnostics.json'
        [wasm test] [17:14:27] info: Killing process tree of 1908...
        [wasm test] 
        [wasm test] [17:14:27] info: Pids to kill: 1908
        [wasm test] 
        [wasm test] [17:14:27] info: Running lldb diagnostics for pid 1908
        [wasm test] 
        [wasm test] [17:14:27] info: Printing backtrace for pid=1908
        [wasm test] 
        [wasm test] [17:14:27] info: lldb was not found, skipping diagnosis..
        [wasm test] 
        [wasm test] XHarness exit code: 70 (TIMED_OUT)
        Exit code: 70

Author: pavelsavara
Assignees: -
Labels:

arch-wasm, test-failure

Milestone: -

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 26, 2022
@pavelsavara pavelsavara added this to the 7.0.0 milestone Jul 26, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 26, 2022
@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Jul 27, 2022
@radical
Copy link
Member

radical commented Jul 27, 2022

@pavelsavara pavelsavara self-assigned this Jul 27, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jul 27, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jul 28, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Aug 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure
Projects
None yet
2 participants