Repository navigation
bench: publish exact three-arm timing and CPU execution evidence - #92
Draft
gspark-etri wants to merge 1 commit into
Draft
gspark-etri wants to merge 1 commit into
gspark-etri wants to merge 1 commit into
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.
Publishes the already completed, independently replayed prepared-state P/C/R timing for #88. Draft stacked on immutable PR89 source1e3c74f; product and measured sources are unchanged. No measurement is rerun.
Retains41 exact fixture/smoke/main archive/report/build/control files and their byte manifest. The common-caller comparison has n=5 per arm: verified-completion medians59.302/46.768/14.670s for cached reconstruction/intact-base copying/admitted consumption. Same complete target cache, independent prepared bases, one ATOM file pair and warm/uncontrolled OS cache; setup remains worker-reported. C/R syscall I/O acceptance, lifecycle, moved-layout and native-usefulness conclusions remain open.
Adds four offline retained-record checks: checked-source exact archive replays and entire saved-report equality; file/source identities; actual pinned CPU Job/Pod ownership/resources/exits/cleanup; retained build/caller identity. No model payload, API key, remote call or device allocation is included. Retained receipt consistency is not remote-execution attestation.
Validation: 77 local Python tests, 73 pass / 4 explicit platform-or-CLI skips; focused four retained-record tests pass. Independent read-only review found no Important issue in the bounded evidence publication. Final CI41493914701 tested merge d0c4b6d of head e1b29c7 into base1e3c74f3c61f8791eadbec704b17df10feb55241. All three jobs succeed and their complete decoded logs were saved and read: 77 Linux Python tests with no skips including actual retained replay, Go race/vet/build, both S3 conformance and CLI roundtrips. No merge has been performed. Existing exact traced-data exporter retains sole Orca transport ownership; traced records are not claimed here.