Repository navigation
Build a template project for each project shape in the image - #68
Open
ihid-assistant[bot] wants to merge 1 commit into
Open
ihid-assistant[bot] wants to merge 1 commit into
ihid-assistant[bot] wants to merge 1 commit into
Conversation
shapes/ holds one template .vbproj for each distinct project file in the track's history since the switch to xUnit v3. At image build, bin/build-shapes.sh builds each one with the SDK and keeps its compiler arguments, its generated source files and its dependencies precompiled with ReadyToRun. The runner is now published with ReadyToRun too. Nothing uses the shapes at run time yet. Co-authored-by: iHiD <286476+iHiD@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BNAndras
approved these changes
Nov 19, 2026
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.
Hello 🙂 I'm working with Claude to try and get our tooling faster.
This PR prepares the templates used by the next PR. It's the third of four that together make this project around 6x faster. I've run it in production to benchmark things in the real world against the most recent few hundred solutions, so I'm confident that it works robustly. However, I've not written the code. I have tried my hardest to get Claude to write sensible messages and comments that explains stuff, but I'd ask for your patience in the fact I'm sending AI code to you. Everything below here is from your friendly neighbourhood LLM...
This is the third of four PRs. Merge them in order: #66, #67, then this one (#68), then #69.
What changed
shapes/folder holds one template project file for each distinct.vbprojthe track has used since it switched to xUnit v3 (5 at the moment). These templates are called shapes.bin/generate-shapes.pywrites them from the track repo's history.bin/build-shapes.shbuilds each shape with the .NET SDK. It saves the compiler arguments, the source files generated by the SDK and packages, and the resolved dependencies. The script also precompiles the dependencies with ReadyToRun, so the test executable starts faster, because the JIT compiler has less to compile. If a shape fails to build, the script removes it./define:"CONFIG=\"release\",...", so the script puts the backslashes back on that line.--prepare-shapeoption, which the script calls after each build. It reduces the shape's.vbprojto its properties,Importitems and package references (seeProjectShape.vb), and saves that as the shape's key. The next PR matches each solution's project file against these keys.This has been tested in production. It doesn't change the median run, which stays at 8.6s.
🤖 Generated with Claude Code