Skip to content

Disable async tests on Wasm R2R - #134643

Open
akoeplinger wants to merge 3 commits into
mainfrom
quarantine-wasm-async-133953
Open

akoeplinger wants to merge 3 commits into
mainfrom
quarantine-wasm-async-133953

Conversation

@akoeplinger

@akoeplinger akoeplinger commented Sep 25, 2026 •

Copy link
Copy Markdown
Member

Summary

Note

This pull request description was generated by GitHub Copilot.

Temporarily disable Async2TaskAdapters.WrapValueVersusAsync only for Wasm ReadyToRun configurations while #133953 tracks the MethodTable validation assertion. Other Wasm modes, platforms, and sibling async tests remain enabled.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: aab39968-c93b-478a-acee-e9f7b2eefc26
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @agocke
See info in area-owners.md if you want to be subscribed.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The targeted quarantine preserves all other test coverage.

Review effort: Lite
Findings: None

What changed in this PR

Temporarily quarantines WrapValueVersusAsync for Wasm ReadyToRun configurations.

Changes:

  • Adds an ActiveIssue linked to issue #133953.
  • Preserves coverage for other configurations.
  • No tests run; attribute-only change.
File Description
src/​tests/​async/​async-versions-task-adapters/​async-versions-task-adapters.cs Adds the scoped Wasm ReadyToRun test exclusion.

The original quarantine allowed the async work item to progress to AwaitNotAsync.AsyncEntryPoint, which hits the same MethodTable SanityCheck assertion tracked by #133953. Quarantine that method under the same Wasm ReadyToRun condition while preserving every other configuration.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: aab39968-c93b-478a-acee-e9f7b2eefc26
Copilot AI review requested due to automatic review settings September 25, 2026 14:40
@akoeplinger akoeplinger changed the title Disable async adapter test on Wasm R2R Disable async tests on Wasm R2R Sep 25, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

No unresolved review issues remain.

Review effort: Lite
Findings: None

After the earlier async quarantines, the Wasm R2R lane reaches GenericVirtualMethod.Program.TestGenericVirtualMethod and asserts in ProcessDynamicDictionaryLookup. Quarantine only that method against #134660 while retaining sibling covariant-return tests and all other configurations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: aab39968-c93b-478a-acee-e9f7b2eefc26
Copilot AI review requested due to automatic review settings September 25, 2026 16:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The targeted quarantines address known failures while preserving broader test coverage.

Review effort: Lite
Findings: None

@lewing

lewing commented Sep 25, 2026

Copy link
Copy Markdown
Member

cc @jakobbotsch

@lewing

lewing commented Sep 25, 2026

Copy link
Copy Markdown
Member

#134676 should fix the underlying issue and we should make sure to reenable the async tests if this merges before it

@akoeplinger

Copy link
Copy Markdown
Member Author

hm yeah looks like there are still more tests that need to be disabled and #134676 seems to be green so yeah maybe let's just take that one.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants