Repository navigation
Record the mlx-train-perf integration proof on the 0.2.0 wheel - #36
Merged
Merged
Conversation
The bundle under evidence/v0.2.0/mlx-train-perf/ was recorded on the published 0.2.0 wheel against mlx-train-perf 0.8.0, the first consumer release that ships the integration, and scanned clean with scripts/scan-evidence-bundle.sh. The integration guide now cites it instead of the 0.1.0-era bundle, and the paragraph about on_parent_exit says this run was recorded under the terminate default. The 0.1.0 bundle stays as the record of the first adapter.
IonDen
added
evidence
The integration guide listed a missing acknowledgement among the bundle's recorded scenarios; that scenario exists only in the 0.1.0 bundle. The bundle README now writes the artifact kind as the report spells it and says the four interrupted-runner runs are hand-driven and not included.
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.
This adds the mlx-train-perf integration proof recorded on the published mlx-guard 0.2.0 wheel, under
evidence/v0.2.0/mlx-train-perf/. The consumer was mlx-train-perf 0.8.0 at its released commit, the first version that ships the integration behind theguardextra. The 0.1.0-era bundle stays in place as the record of the first adapter.The run is a 1,000-repetition real MLX loss-layer condition under a 512 MiB footprint limit and a 500 ms wall limit. The supervisor requested a checkpoint at 501 ms, the worker wrote and synced a partial artifact at repetition 278 and returned path-free metadata, the supervisor accepted it at 531 ms, sent TERM, and finalized at 554 ms with nothing left running. The bundle README lists the failure paths the consumer's tests pin, which of them run the real supervisor, and the four things the first consumer had to learn from the 0.2.0 client (fallback by call site, one report path per attempt, the distribution name in
PackageNotFoundError, surviving a failed checkpoint).docs/integrations/MLX_TRAIN_PERF.mdnow links this bundle in both places that cited the 0.1.0 one, and itson_parent_exitparagraph says this run was recorded under theterminatedefault rather than predating it. One CHANGELOG bullet under Unreleased. The bundle passedscripts/scan-evidence-bundle.shwith the host name and user as extra literals. No code changes.