Repository navigation
Resume benchmarks without repeatedly exporting completed cases - #8
Merged
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.
Resuming a run previously re-entered every completed case, regenerated aggregate reports and recompressed the complete results ZIP repeatedly. Application 1.3.1 verifies saved fork pairs in one scan, restores their results in case order, and enters the measurement loop only for unfinished or corrupt cases. Completed cases keep their original fork/checkpoint files. Fork checkpoints remain immediate and synchronized; ZIP exports are limited to once a minute with forced completion/interruption snapshots. Short Windows AccessDenied rename failures are retried without deleting the previous file or ignoring write failures.
Add an explicit -UpgradeResume PowerShell option for stopped published 1.3.0 runs. The helper requires the exact original release SHA-256, locks and backs up the request, and byte-compares the two applications, allowing only audited resume/export classes, its added helper and application version metadata. Numerical harness sources, dependency classes, case-model class and other launcher classes must match. Only the application fingerprint is migrated, with provenance; normal configuration/binary/machine checks and fork checksums remain enforced. Without the option, existing runs retain their original runner automatically.
Validation: 16 local launcher tests, including checkpoint preservation, stable case ordering, 640 suppressed ZIP refreshes, forced final export and refusal of changed numerical/dependency content. CI checks Windows/Linux all-library smoke, fast resume with no completed-case loop, and a real published 1.3.0 upgrade with unchanged fork hashes before publication. Benchmark inputs, algorithms, case plan, JMH timing settings and comparison dependency pins are unchanged.