-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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] Stack overflow in JIT/Directed/tailcall/tailcall/tailcall.sh
on Linux
#69517
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsTwo tests failing with stack overflow on unrelated PR, build, and log:
And:
This was seen on other recent runs too.
|
@radical please open an meta issue with stack overflow related wasm problems and disable tests that are failing due to it. There is discussion spread across multiple issues right now. |
`JIT/Directed/tailcall/tailcall/tailcall.sh` Issue: dotnet#69517
* [wasm] Disable runtime test failing due to stack overflow `JIT/Directed/tailcall/tailcall/tailcall.sh` Issue: #69517 * Also disable JIT/Directed/IL/Tailcall/ExplicitTailCallNoSO/ExplicitTailCallNoSO.sh * try to fix the exclusion * Fix path for exclusion
* [wasm] Disable runtime test failing due to stack overflow `JIT/Directed/tailcall/tailcall/tailcall.sh` Issue: dotnet#69517 * Also disable JIT/Directed/IL/Tailcall/ExplicitTailCallNoSO/ExplicitTailCallNoSO.sh * try to fix the exclusion * Fix path for exclusion
These tailcall tests fail because we run with debugger enabled, which disables all optimizations, including tailcall optimization. This means that it is normal to fail with stack overflow exception. Did we just recently start running these tests with debug enabled on wasm ? |
What exactly would this mean? Building in debug config? |
I recently added https://github.com/dotnet/runtime/blob/main/src/mono/wasm/build/WasmApp.targets#L108-L109 and https://github.com/dotnet/runtime/blob/main/src/mono/wasm/test-main.js#L423-L425 . But these should get triggered only when |
I'll check locally |
Fixes dotnet#69517 - Recent [wasm-app-host commit](6b3ea40) changed `WasmApp.targets` so `WasmDebugLevel` would be set to enable debugging if `Configuration==Debug`. - this broke some runtime tests which depend on tail call optimizations, which get disabled when debugging is enabled in the runtime. - And the wasm apps for the runtime tests are being built with no configuration set, which defaults to `Debug`. Instead, propogate the config for the build to the wasm proxy (`WasmTestRunner`) projects too. Fixes dotnet#69517 .
Opened #70050 to fix this. |
…70050) * [wasm] Fix runtime test failing due to the app running in debug mode Fixes #69517 - Recent [wasm-app-host commit](6b3ea40) changed `WasmApp.targets` so `WasmDebugLevel` would be set to enable debugging if `Configuration==Debug`. - this broke some runtime tests which depend on tail call optimizations, which get disabled when debugging is enabled in the runtime. - And the wasm apps for the runtime tests are being built with no configuration set, which defaults to `Debug`. Instead, propogate the config for the build to the wasm proxy (`WasmTestRunner`) projects too. Fixes #69517 . * Revert "[wasm] Disable runtime test failing due to stack overflow (#69863)" This reverts commit 61441fa.
Two tests failing with stack overflow on unrelated PR, build, and log:
And:
This was seen on other recent runs too.
The text was updated successfully, but these errors were encountered: