Repository navigation
Runbook 0.8: how long to test the memory - #26
Merged
Merged
Conversation
Four passes at least, longer if it can run overnight, and why a clean first pass proves little. The rule about borg check --repair stays. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Section 0.8 of the deployment runbook now says to run memtest86+ for four passes at least, longer if it can run overnight, because a weak cell may fail only once every hour or two and a clean first pass proves little. The first pass takes about 30 minutes for 16 GB, the later ones longer. The rule not to install, and not to run
borg check --repair, on memory that has not passed stays.Documentation only: the CI's
docscheck covers it;lab/gate.shdoes not apply.🤖 Generated with Claude Code