[browser] Remove traces of AOT on helix

Open Beginner friendly
#133,363 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, wasm
Domain
build-system, testing-qa

Research direction

Start with eng/testing/tests.wasm.targets around the _BundleAOTTestWasmAppForHelix target and src/mono/wasm/data/aot-tests/ProxyProjectForAOTOnHelix.proj. Search these paths and related build files for remaining AOT-on-Helix references, then verify that the obsolete traces are gone without breaking the relevant build configuration.

Written by the indexing model from the issue text.

Description

arch-wasm area-Infrastructure-mono os-browser

Targets like _BundleAOTTestWasmAppForHelix

https://github.com/dotnet/runtime/blob/294fe754ccc3db80640c7e34018d97cfac834f51/eng/testing/tests.wasm.targets#L128

https://github.com/dotnet/runtime/blob/294fe754ccc3db80640c7e34018d97cfac834f51/src/mono/wasm/data/aot-tests/ProxyProjectForAOTOnHelix.proj#L1

Dominant language
C#
Stars
18.3k
Forks
5.6k
Avg merge
2d 19h
Merged PRs (30d)
589

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.