Skip to content

Release prep for 0.4.8: Ctrl+C at stock, 0.4.2 config test, release checks - #59

Merged
Rovey merged 3 commits into
mainfrom
release-prep-0.4.8
Oct 18, 2026
Merged

Rovey merged 3 commits into
mainfrom
release-prep-0.4.8

Conversation

@Rovey

@Rovey Rovey commented Oct 18, 2026

Copy link
Copy Markdown
Owner

What changes

  • Ctrl+C during the measurement at stock stops the run and puts the tune back. measure_stock did not register the emergency handlers, so Ctrl+C on the command line ended gao there: the tune the run found on the card was not put back, and a running tray app took the stock it left for a driver reset.
  • The put-back after a stopped run gets no run.log header of its own, so the log no longer reads as if a new run started.
  • Test: a gao.json written by 0.4.2 keeps its tune and applies at logon. Everyone on 0.4.2 (the latest release) will be offered 0.4.8; a Best and an All in one profile in 0.4.2's exact format load whole and pass decide_boot.
  • README: what the RTX 5070 showed about the desktop after a driver reset, gao --stress --duty, and the dashboard's comparison with stock.
  • Hardware checks 30, 31, 34, 37, 38, 39, 42, 43, 44, 47 and 56 filled in from the release checks of 2026-10-18 on the reference RTX 4070, or pointed at the later checks that covered them.

Checked

  • Release build, all tests and ASan green.
  • On the reference RTX 4070 (driver 617.42), elevated, with the installed 0.4.8-rc8 and a build of this branch:
    • Ctrl+C 10 s into the measurement at stock: the run ended in 1.2 s, the saved tune was back, fans driver control, journal ABORTED.
    • Check 43: gao --fan auto under load, the tray put its curve back within 45 s.
    • Check 34: an outside core offset (gao --set-core 30); the watchdog logged that another program changed the settings and left them alone.
    • Check 37: the close button hides the window to the tray.
    • Check 47: Abort a minute into the soak of a Best of my GPU run from the window: aborted within a second, journal ABORTED, the saved tune back on the card, no watchdog line after it.
  • Not run: check 42 (no program here sets the fans by hand).

🤖 Generated with Claude Code

Rovey and others added 3 commits October 18, 2026 20:12
…at logon

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ts the tune back

measure_stock did not register the emergency handlers, so Ctrl+C on the
command line ended gao there: the tune the run found on the card was not
put back, and a running tray app took the stock it left for a driver reset.
The README now says what the RTX 5070 showed about the desktop after a
driver reset, lists gao --stress --duty, and names the dashboard's
comparison with stock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…its own

After Ctrl+C the CLI wrote `=== gpu-auto-optimizer <version>` before the
line that says the tune is back, so run.log read as if a new run had
started. logged() takes `header = false` for lines that belong to the run
before them.

Hardware checks 30, 31, 34, 37, 38, 39, 42, 43, 44, 47 and 56 are filled
in from the release checks of 2026-10-18 on the reference card (or point
at the later checks that covered them).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Rovey
Rovey merged commit 40ee720 into main Oct 18, 2026
2 checks passed
@Rovey
Rovey deleted the release-prep-0.4.8 branch October 18, 2026 18:42
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