Skip to content

fix(cli): gao --status advises the retest after a driver update - #71

Merged
Rovey merged 1 commit into
mainfrom
fix/status-driver-retest
Nov 5, 2026
Merged

Rovey merged 1 commit into
mainfrom
fix/status-driver-retest

Conversation

@Rovey

@Rovey Rovey commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Why

After a driver update (seen on the RTX 5070, 617.14 -> 621.14) gao --status said:

driver:     621.14 (CHANGED -- run `gao --optimize` again)

That is the 40-minute run. The logon apply gives other advice: the five-minute retest, which here passed and saved the tune for 621.14.

What

  • kDriverChangedAdvice in core/boot.hpp: one text for both places.
  • driver_status(tested_on, now): matches, CHANGED from 617.14 -- test the tune again in the app (5 minutes, or gao --retest), or optimize again, or, when NVML reports no version, NVML did not report it; the tune is not applied at logon (it used to read unknown (CHANGED ...)).
  • decision_text (the logon apply) uses the same advice; its text is unchanged.

The gpu: line still advises gao --optimize: a retest is for a new driver, not a new card.

Tests

  • cmake --workflow --preset ci: builds with /W4 /WX; core_tests 457/457 and app_tests pass. New test: the advice after an update names gao --retest and not gao --optimize, a matching driver says matches, an unknown one does not say CHANGED.
  • gao --status of this build on the RTX 5070 (driver 621.14, after the retest): driver: 621.14 (matches). The changed case was not seen on the card: the driver matches again.

🤖 Generated with Claude Code

The driver line said "CHANGED -- run `gao --optimize` again", a 40-minute
run, where the logon apply advises the five-minute retest. Both now use
one advice (kDriverChangedAdvice). The line also names the driver the
tune was tested on, and an unreported version no longer reads as
"CHANGED".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Rovey
Rovey merged commit e7ee471 into main Nov 5, 2026
2 checks passed
@Rovey
Rovey deleted the fix/status-driver-retest branch November 5, 2026 22:29
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