[TRTLLM-14571][infra] Enable container-local AutoTuner cache in CI#16794
[TRTLLM-14571][infra] Enable container-local AutoTuner cache in CI#16794YihuiLu512 wants to merge 1 commit into
Conversation
- Wire TLLM_AUTOTUNER_CACHE_PATH into pytest stages to reuse tactic profiling across testcases via a volatile container-local /tmp path. - Harden _deserialize_cache_data to skip non-literal tactics (SyntaxError) instead of crashing load_cache, e.g. Fp4QuantTactic IntEnum reprs. - Add regression test for the skip-on-load behavior. Signed-off-by: Yihui Lu <269394165+YihuiLu512@users.noreply.github.com>
|
/bot run |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (3)
WalkthroughThe PR configures pytest runs to use a container-local AutoTuner profiling cache and updates cache deserialization to skip tactic entries that raise ChangesAutotuner cache reliability
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #61274 [ run ] triggered by Bot. Commit: |
|
PR_Github #61274 [ run ] completed with state
|
The goal is to improve GPU utilization during CI runs.
Dev Engineer Review
/tmpAutoTuner profiling cache, enabling tactic reuse without affecting host or shared caches.SyntaxError, log once, and skip invalid non-literal tactic entries instead of failing the entire cache load.QA Engineer Review
test_load_cache_skips_non_literal_tactic().tests/integration/test_lists/coverage was identified; the test is not listed in CItest-db/or manual QAqa/files.Description
Test Coverage
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.