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

Mono Browser wasm Release failures on runtime rolling build #69850

Closed
mkhamoyan opened this issue May 26, 2022 · 6 comments · Fixed by #69863
Closed

Mono Browser wasm Release failures on runtime rolling build #69850

mkhamoyan opened this issue May 26, 2022 · 6 comments · Fixed by #69863
Labels

Comments

@mkhamoyan
Copy link
Contributor

Description

Last rolling build of runtime fails with following exceptions

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at ExplicitTailCallNoSO.CalculateSumWithTailCall(Int32 n, Int32 sum

or

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at Class1.Recurse4(Int32 depth, Object o1, Object o2)
for more info please look https://dev.azure.com/dnceng/public/_build/results?buildId=1790753&view=ms.vss-test-web.build-test-results-tab

Reproduction Steps

Check last rolling build of runtime https://runfo.azurewebsites.net/view/build/?number=1790753

Expected behavior

Tests should pass

Actual behavior

[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@ghost ghost added the untriaged New issue has not been triaged by the area owner label May 26, 2022
@dotnet-issue-labeler dotnet-issue-labeler bot added area-ExceptionHandling-coreclr and removed untriaged New issue has not been triaged by the area owner labels May 26, 2022
@mkhamoyan
Copy link
Contributor Author

mkhamoyan commented May 26, 2022

From commits seems it can be related this PR , @radical could you please check? can it be related?

@radical
Copy link
Member

radical commented May 26, 2022

This was failing before that PR too - #69517

@radical
Copy link
Member

radical commented May 26, 2022

And the other failure is #43200

@mkhamoyan
Copy link
Contributor Author

mkhamoyan commented May 26, 2022

I see , in rolling build it was hit first time in last 2 weeks. So we will disable tests?

@radical
Copy link
Member

radical commented May 26, 2022

Yeah, I can disable JIT/Directed/tailcall/tailcall/tailcall.sh. Based on #43200 (comment), I think we don't need to disable JIT/Performance/CodeQuality/Linq/Linq/Linq.sh.

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label May 26, 2022
@radical radical added the arch-wasm WebAssembly architecture label May 26, 2022
@ghost
Copy link

ghost commented May 26, 2022

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

Issue Details

Description

Last rolling build of runtime fails with following exceptions

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at ExplicitTailCallNoSO.CalculateSumWithTailCall(Int32 n, Int32 sum

or

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at Class1.Recurse4(Int32 depth, Object o1, Object o2)
for more info please look https://dev.azure.com/dnceng/public/_build/results?buildId=1790753&view=ms.vss-test-web.build-test-results-tab

Reproduction Steps

Check last rolling build of runtime https://runfo.azurewebsites.net/view/build/?number=1790753

Expected behavior

Tests should pass

Actual behavior

[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: mkhamoyan
Assignees: -
Labels:

arch-wasm, area-ExceptionHandling-coreclr, in-pr

Milestone: -

@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label May 27, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jun 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants