[TRTLLM-15115][test] Prune Starcoder2-3B functional and unit tests - #17674
Conversation
|
/bot run --stage-list "a100" |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan includes up to 12 reviews per rolling hour; 11 remain after this review. WalkthroughThe PR removes StarCoder2-3B from accuracy references, integration test parameters, model fixtures, performance configurations, timing data, attention settings, modeling tests, and tokenizer test parameters. ChangesStarCoder2-3B coverage removal
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change prunes Starcoder2-3B test coverage while retaining Starcoder2-7B/15B coverage; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #66167 [ run ] triggered by Bot. Commit: |
|
PR_Github #66167 [ run ] completed with state
|
|
/bot run --gpu-type "A100X" |
|
PR_Github #66202 [ run ] triggered by Bot. Commit: |
|
PR_Github #66202 [ run ] completed with state
|
|
/bot run --gpu-type "A100X" --disable-fail-fast |
|
PR_Github #66296 [ run ] triggered by Bot. Commit: |
Remove out-of-scope Starcoder2-3B coverage per Test Scope Review 2026.7, including QA/CI list entries, encode/cli harnesses, and 3B-specific unit tests while leaving StarCoder2-7B/15B coverage intact. Signed-off-by: Xin He (SW-GPU) <200704525+xinhe-nv@users.noreply.github.com>
|
PR_Github #66296 [ run ] completed with state |
Signed-off-by: xinhe-nv <200704525+xinhe-nv@users.noreply.github.com>
Signed-off-by: xinhe-nv <200704525+xinhe-nv@users.noreply.github.com>
|
/bot reuse-pipeline |
Signed-off-by: xinhe-nv <200704525+xinhe-nv@users.noreply.github.com>
Drop the remaining StarCoder2 allclose unit coverage after the 3B prune. Signed-off-by: Xin He (SW-GPU) <200704525+xinhe-nv@users.noreply.github.com>
|
/bot reuse-pipeline |
|
PR_Github #66642 [ reuse-pipeline ] triggered by Bot. Commit: |
|
PR_Github #66642 [ reuse-pipeline ] completed with state |
…VIDIA#17674) Signed-off-by: Xin He (SW-GPU) <200704525+xinhe-nv@users.noreply.github.com>
Remove out-of-scope Starcoder2-3B coverage per Test Scope Review 2026.7, including QA/CI list entries, encode/cli harnesses, and 3B-specific unit tests while leaving StarCoder2-7B/15B coverage intact.
Dev Engineer Review
QA Engineer Review
TestStarcoder2_3BCLI accuracy coverage.test_starcoder2_multi_lora,STARCODER2_3B_CONFIG, and related StarCoder2-3B modeling scenarios.tests/integration/test_lists/qa/llm_function_core.txttests/integration/test_lists/test-db/l0_a100.ymlDescription
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.