Repository navigation
ci: restore normal release checks and checkpoint compatibility - #16
Merged
Merged
Conversation
Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
Signed-off-by: Robert Washbourne <rawashbourne@gmail.com>
rawsh
changed the title
rawsh
force-pushed
the
fix/release-ci-coverage
branch
from
October 21, 2026 12:03
b3fe298 to
cd89abf
Compare
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.
Release-targeted PRs omit the normal test workflow, and the existing release tree fails its static and checkpoint controls. Enable the existing jobs for release/v0.* without changing their coverage.
The exact release-base control reproduced 22 mypy findings and 17 test failures before these changes. Match annotations to existing asynchronous checkpoint receipts and validated gather results; preserve ordinary None returns. Existing route packing also assumes Tensor.names exists, which fails on the supported hosted Torch 2.14.1 CPU build: retain the named fallback when that metadata exists and accept ordinary tensors when the API is absent. Finally, update the old atomic-save fixture to distinguish controller failure before writers start from storage-fanout failure: both must leave the committed directory absent, while possible storage writers retain staging and their failed Future. Checkpoint snapshotting, settlement, ownership, I/O and wire algorithms are unchanged.
Ruff, formatting and diff checks pass. Normal full repository CI is pending; no status override or runtime adoption. Codec performance work remains separate in PR15. The annotation-only PR17 is included here to test the complete release-CI repair.
AI assistance: Codex.