Add adaptive scheduling and trustworthy benchmark tooling - #14
Merged
Conversation
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.
What changed
auto = CPU countwith adaptive worker selection based on schedulable units, process-visible capacity, duration history, startup cost, and predicted makespantestenix tune/testenix benchmarkwith safe configuration persistence--shard-modulesscheduling and trusted collection manifests to avoid the collection-side import on unchanged suites--no-historyWhy
The previous defaults could oversubscribe high-core machines, hide module-affinity bottlenecks, import test modules twice, and make benchmark claims without enough provenance. The new paths are adaptive or explicitly opt-in, and publication gates fail closed on stale inventories, mismatched per-test outcomes, ambiguous runner targets, dirty repositories, or unverified runtimes.
Validation
d355a457Notes
This PR does not publish a new release and does not replace the historical 3.15x baseline with an unreviewed number. The local real-project measurements remain explicitly non-publishable because the target checkout was dirty and this code is unreleased.