Skip to content

docs(development): how to check a change on your own card - #70

Merged
Rovey merged 1 commit into
mainfrom
docs/own-card-checks
Nov 5, 2026
Merged

Rovey merged 1 commit into
mainfrom
docs/own-card-checks

Conversation

@Rovey

@Rovey Rovey commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Summary

A section under Testing in docs/development.md for anyone who wants to check a change, or report a result, on their own NVIDIA card:

  • Before a run: copy gao.json, close programs on the card (gao --busy says none), run with the window closed, elevated only for writes.
  • Test the changed part first (links the list in AGENTS.md).
  • Which run.log lines matter: other programs on the card, a planned driver reset in the search against one worth reporting, the undervolt step, RESULT:.
  • A driver reset in the Windows logs (nvlddmkm 14 with Display 153), and the black desktop after one.
  • Where to report: the Result on my card template, or a row in hardware-checks.md.

Docs only.

Test plan

  • The log wording matches the source (search.cpp, undervolt.cpp, stability.cpp)
  • Read the rendered section and the AGENTS.md anchor link on the branch page

🤖 Generated with Claude Code

Before a run, what to close, which run.log lines matter (a planned driver
reset against one worth reporting), the Windows events of a reset, the
black desktop after one, and where to report.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Rovey
Rovey merged commit eb7241b into main Nov 5, 2026
2 checks passed
@Rovey
Rovey deleted the docs/own-card-checks branch November 5, 2026 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant