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] Fix runtime test failing due to the app running in debug mode #70050

Merged
merged 2 commits into from
Jun 1, 2022

Conversation

radical
Copy link
Member

@radical radical commented May 31, 2022

Fixes #69517

  • Recent wasm-app-host commit 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.

radical added 2 commits May 31, 2022 20:57
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 .
@radical radical added arch-wasm WebAssembly architecture disabled-test The test is disabled in source code against the issue area-VM-meta-mono labels May 31, 2022
@radical radical requested review from lewing and BrzVlad May 31, 2022 21:00
@ghost ghost assigned radical May 31, 2022
@ghost
Copy link

ghost commented May 31, 2022

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

Issue Details

Fixes #69517

  • Recent wasm-app-host commit 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 .

Author: radical
Assignees: -
Labels:

arch-wasm, disabled-test, area-VM-meta-mono

Milestone: -

Copy link
Member

@thaystg thaystg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@radical radical merged commit 174a894 into dotnet:main Jun 1, 2022
@radical radical deleted the fix-tail-call-tests branch June 1, 2022 19:05
@ghost ghost locked as resolved and limited conversation to collaborators Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono disabled-test The test is disabled in source code against the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[wasm] Stack overflow in JIT/Directed/tailcall/tailcall/tailcall.sh on Linux
2 participants