Repository navigation
Update scenarios README profiles to match current available profiles - #7
Closed
LoopedBard3 wants to merge 3 commits into
Closed
LoopedBard3 wants to merge 3 commits into
LoopedBard3 wants to merge 3 commits into
Conversation
* Update RazorSlices to 0.11.0 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update RazorSlicesVersion to 0.11.1 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Sébastien Ros <sebastienros@gmail.com>
These scenarios all hang/crash in crossgen2 with IndexOutOfRangeException on .NET 11 preview SDKs that predate dotnet/runtime#129053 ("Fix composite R2R token corruption for devirtualized async-variant callees", merged 2026-06-06). The repro hits Kestrel's Http1ChunkedEncodingMessageBody.PumpAsync during composite R2R compilation; crossgen2 then fails to terminate, causing the crank-agent 10-minute build timeout we saw on 2026-06-08. build/singlefile-scenarios.yml: add per-mode `condition` field (threaded into the crank job condition) and set 'false' for Single-file, Trimmed, R2RComposite-Windows, R2RComposite-Linux. build/crossgen2-scenarios.yml: enrich the existing disable note on "CG2 composite" / "CG2 composite avx2" (already disabled by aspnet#2177) with a pointer to the upstream runtime fix. build/nativeaot-scenarios.yml: set condition to 'false' on the three Goldilocks "Trim R2R SingleFile" jobs (Stage1, Stage2, gRPC Stage1). Self-contained, AOT, non-composite R2R, and all NativeAOT scenarios remain enabled - the bug is composite-R2R-specific. Re-enable once the runtime fix flows into the .NET 11 SDK consumed by the benchmark agents. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The profiles table listed five EOL'd machines (aspnet-perf-lin, aspnet-perf-win, aspnet-citrine-lin, aspnet-citrine-win, aspnet-citrine-amd2) that were removed in aspnet#2169, and was missing aspnet-citrine-arm-win. Update the table to the current public profiles and repoint all sample commands that referenced retired profiles to aspnet-gold-lin/aspnet-gold-win. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
scenarios/README.mdProfiles section was out of date with the actual crank profiles defined inaspnet.profiles.yml/aspnet.profiles.standard.yml.Profiles table
aspnet-perf-lin,aspnet-perf-win,aspnet-citrine-lin,aspnet-citrine-win,aspnet-citrine-amd2.aspnet-citrine-arm-win(ARM/Windows, 80 cores) alongside the still-validaspnet-citrine-arm-lin,aspnet-gold-lin,aspnet-gold-win, andlocal.Sample commands
aspnet-perf-lin→aspnet-gold-linaspnet-perf-win/aspnet-citrine-win→aspnet-gold-winProfile names were validated against
scenarios/aspnet.profiles.ymlandscenarios/aspnet.profiles.standard.yml.