Skip to content

[CI] Validate GPU frequency before GPU jobs#225

Draft
RMLYC wants to merge 2 commits intotile-ai:mainfrom
RMLYC:fix/ci/gpu-frequency-1830-check
Draft

[CI] Validate GPU frequency before GPU jobs#225
RMLYC wants to merge 2 commits intotile-ai:mainfrom
RMLYC:fix/ci/gpu-frequency-1830-check

Conversation

@RMLYC
Copy link
Collaborator

@RMLYC RMLYC commented Feb 27, 2026

Closes #216

Summary

  • add a GPU pre-check step in CI GPU jobs to read current graphics clock
  • validate all detected GPUs are running at 1830 MHz with retries and clear per-GPU logs
  • fail early when GPU frequency is not 1830 MHz to avoid unreliable test runs

Test plan

  • PRE_COMMIT_HOME=/tmp/pre-commit-cache pre-commit run --all-files
  • GPU frequency check execution on self-hosted runner (to be validated in CI)

@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@RMLYC RMLYC added the ci label Feb 27, 2026
@RMLYC RMLYC marked this pull request as draft February 27, 2026 04:13
@RMLYC RMLYC changed the title [CI] Validate GPU frequency lock before GPU jobs [CI] Validate GPU frequency before GPU jobs Feb 27, 2026
@RMLYC RMLYC added the all ai powered Issue or Pull request all finished by AI label Feb 27, 2026
@xZacky
Copy link
Collaborator

xZacky commented Feb 27, 2026

Checking GPU frequency before testing is not feasible, because after frequency locking, if there is no workload on the GPU, the frequency will still remain very low.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

all ai powered Issue or Pull request all finished by AI ci

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] CI should verify GPU frequency to ensure correct execution

2 participants