Repository navigation
Release v2.0.0-beta.18 with TensorRails DMTCP v5.0.0-warmctl.2 - #74
Merged
Merged
Conversation
The fork release leaves resident zero pages out of a checkpoint and lets the restart readers share the runs between them. Its archives' checksums are pinned from the published release, whose provenance attestations verify; fetch-dmtcp.sh accepts both architectures against them. The changelog's Unreleased section, with the stage zero-page fix, becomes v2.0.0-beta.18.
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.
Bumps the bundled DMTCP to v5.0.0-warmctl.2 (TensorRails/dmtcp#4) and names the changelog's Unreleased section v2.0.0-beta.18, so the tag can be cut after merge.
internal/dmtcp/VERSIONandSHA256SUMS: checksums copied from the published release; all three archives passgh attestation verify, andscripts/fetch-dmtcp.shfetches amd64 and arm64 against them (BUILDINFO: commit 95b7da77, Debian 12, glibc 2.36)./health4.6–5.1 → 4.0–4.4 s, same answers. Pinned CUDA host memory already left its zeros out, so the H200 Qwen3.8-Flash-Next CPU-side table is unchanged.docs/dmtcp.mdpoints at the new release and says what it adds.Checks:
go test ./..., golangci-lint v2.14.0 with GOOS=linux (0 issues),ruff check python. The release workflow runs on this PR as a snapshot.After merge: tag v2.0.0-beta.18, publish the runtime images (
runtime-image.yml, as for beta.17: default base and-vllm032), bake and cold-start on a GPU, then movelatest.