LLM Benchmarks: Use stable model IDs and clean up build outputs - #6034
Open
bradleyshep wants to merge 4 commits into
Open
bradleyshep wants to merge 4 commits into
bradleyshep wants to merge 4 commits into
Conversation
bradleyshep
requested review from
bfops,
cloutiertyler and
jdetter
as code owners
October 1, 2026 15:19
This branch has not been deployed
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.
Description of Changes
Use stable API model IDs for benchmark results and uploads. Display-name changes will no longer create separate entries for the same model.
Remove task-local Rust, C#, and TypeScript build outputs after publishing, including failed attempts. Preserve source files and shared caches. Add disk-usage logs before and after benchmarks.
API and ABI breaking changes
No public API or ABI changes. Benchmark result keys now contain model IDs instead of display names.
Rollback safety impact
No database schema changes. Reverting restores display-name keys and can create duplicate model entries on subsequent uploads.
Expected complexity level and risk
2/5. Changes are limited to the benchmark tool and workflow. Cleanup only targets task-local build directories.
The C# server SIGKILL remains unresolved; this PR does not claim to fix it.
Testing