[perf][wasm] Stage Crossgen2 pack for CoreCLR R2R benchmarks by lewing · Pull Request #133040 · dotnet/runtime

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

lewing · 2026-09-01T19:38:58Z

Summary

Stage the matching locally built, non-symbol Microsoft.NETCore.App.Crossgen2 package in the BrowserWasmCoreCLR performance artifact under staging/built-nugets.

This enables isolated Helix machines to resolve the same-build Crossgen2 pack when per-application browser-WASM benchmarks publish with PublishReadyToRun=true. The CoreCLR performance build enables BuildHostTools, and the pack subset permits browser builds with that explicit opt-in to run Microsoft.NETCore.App.Crossgen2.Host.sfxproj. The package selection excludes *.symbols.nupkg and fails if no matching non-symbol package is available. These changes apply only to BrowserWasmCoreCLR; Mono artifact behavior is unchanged.

End-to-end runtime-wasm-perf validation depends on the companion dotnet/performance change currently at commit 17449e9826d0ecc224e92a3ad854796b0be41219.

Validation

Parsed the changed XML and YAML build configuration.
Ran git diff --check and commit checks.
Simulated staging with matching non-symbol, symbols, and unrelated nupkgs; only the non-symbol Crossgen2 package was copied.
Evaluated the MSBuild project graph and confirmed:
- browser CoreCLR with BuildHostTools=true includes Microsoft.NETCore.App.Crossgen2.Host.sfxproj;
- browser CoreCLR without the opt-in excludes it;
- Android remains excluded even with BuildHostTools=true.

Note

This pull request was generated with the assistance of GitHub Copilot.

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

azure-pipelines · 2026-09-01T19:40:02Z

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

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

Copilot

🟢 Approval recommended

The changes are narrowly scoped to the CoreCLR browser-wasm perf pipeline and the updated conditions/staging logic are consistent with existing TargetsMobile semantics for TargetOS=browser.

Pull request overview

This PR updates the WASM performance build to produce and stage the host Crossgen2 pack alongside the CoreCLR browser-wasm performance artifact, enabling downstream R2R publishing on isolated machines using same-build assets.

Changes:

Allow building the Crossgen2 host pack when TargetOS=browser and BuildHostTools=true (even though browser sets TargetsMobile=true).
Add an optional pipeline step to copy the non-symbol Microsoft.NETCore.App.Crossgen2.*.nupkg into the staged built-nugets feed and fail if none is present.
Enable BuildHostTools=true for the CoreCLR browser-wasm perf build job and turn on Crossgen2 pack staging for its artifact.

File summaries

File	Description
eng/Subsets.props	Adjusts pack-building conditions so browser-wasm CoreCLR builds can produce the host Crossgen2 pack when opted in.
eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml	Adds an opt-in step to stage only non-symbol Crossgen2 nupkgs into the perf artifact’s local feed.
eng/pipelines/performance/templates/perf-wasm-build-jobs.yml	Opts the CoreCLR browser-wasm perf job into `BuildHostTools` and Crossgen2 pack staging.

Review details

Files reviewed: 3/3 changed files
Comments generated: 0
Review effort level: Lite

azure-pipelines · 2026-09-02T02:37:17Z

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

lewing · 2026-09-02T03:27:23Z

dotnet/performance#5297 is the consuming side once this lands

pavelsavara · 2026-09-02T07:15:52Z

is @radekdoulik doing the same thing in #131877 ?

dotnet-policy-service · 2026-09-02T12:15:50Z

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

lewing · 2026-09-02T13:32:40Z

/ba-g failures are not related

[perf][wasm] Stage Crossgen2 pack in CoreCLR artifact
b72d7d8
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

github-actionsBot added the area-Build-mono label Sep 1, 2026

dotnet-policy-serviceBot assigned lewing Sep 1, 2026

lewing requested a review from kotlarmilos September 1, 2026 19:53

lewing added 2 commits September 1, 2026 15:56

[perf][wasm] Build host Crossgen2 pack
a3fd901
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

[perf][wasm] Allow browser host Crossgen2 pack
4c4f965
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4188acf-cdd7-467f-818f-5a43eaaf9e3e

lewing requested a lite review from Copilot September 1, 2026 23:42

Copilotstarted reviewing on behalf of lewing September 1, 2026 23:43 View session

CopilotAI reviewed Sep 1, 2026
View reviewed changes

lewing mentioned this pull request Sep 2, 2026
Use apt lock timeout for prerequisites dotnet/performance#5296
Open

lewing marked this pull request as ready for review September 2, 2026 02:36

lewing requested a review from akoeplinger as a code owner September 2, 2026 02:36

lewing requested a review from ilonatommy September 2, 2026 02:36

lewing mentioned this pull request Sep 2, 2026
Add CoreCLR WASM R2R performance lane dotnet/performance#5297
Draft

This was referenced Sep 2, 2026
Android WebSocket failure #121518
Open
Assertion failure in ConnectAsync_WithBuffer_Succeeds on Android/MacCatalyst/tvOS (Mono/CoreCLR/NativeAOT) #125825
Open

maraf approved these changes Sep 2, 2026
View reviewed changes

pavelsavara mentioned this pull request Sep 2, 2026
[wasm] Compute CoreCLR P/Invoke struct sizes with crossgen2's type system #131877
Open

pavelsavara added arch-wasm WebAssembly architecture area-ReadyToRun and removed area-Build-mono labels Sep 2, 2026

pavelsavara added this to the 12.0.0 milestone Sep 2, 2026

lewing merged commit 399c3eb into mainSep 2, 2026
202 of 204 checks passed

lewing deleted the lewing-wasm-r2r-perf-artifact branch September 2, 2026 14:19