-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[TRTLLM-8269][test] do not explicitly pass temperature=0 to select greedy sampling #7909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/bot run --disable-multi-gpu-test --disable-fail-fast |
a83732b
to
a377ade
Compare
PR_Github #19610 [ run ] triggered by Bot |
a377ade
to
4dd01b7
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19613 [ run ] triggered by Bot |
PR_Github #19610 [ run ] completed with state |
/bot kill |
PR_Github #19617 [ kill ] triggered by Bot |
PR_Github #19613 [ run ] completed with state |
PR_Github #19617 [ kill ] completed with state |
4dd01b7
to
669f56f
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19665 [ run ] triggered by Bot |
PR_Github #19665 [ run ] completed with state |
669f56f
to
c8ca47f
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19822 [ run ] triggered by Bot |
PR_Github #19822 [ run ] completed with state |
c8ca47f
to
0aa4358
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19943 [ run ] triggered by Bot |
PR_Github #19943 [ run ] completed with state |
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19973 [ run ] triggered by Bot |
0aa4358
to
ef8777d
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #19980 [ run ] triggered by Bot |
PR_Github #19973 [ run ] completed with state |
PR_Github #19980 [ run ] completed with state |
ef8777d
to
e923abc
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #20077 [ run ] triggered by Bot |
e923abc
to
704809b
Compare
/bot run --disable-multi-gpu-test --disable-fail-fast |
PR_Github #20091 [ run ] triggered by Bot |
PR_Github #20077 [ run ] completed with state |
PR_Github #20091 [ run ] completed with state |
Signed-off-by: ixlmar <[email protected]>
704809b
to
ad602ed
Compare
/bot run |
PR_Github #20108 [ run ] triggered by Bot |
PR_Github #20108 [ run ] completed with state |
📝 WalkthroughWalkthroughRemoved explicit temperature=0 usage from sample generation and tests. Adjusted generate_samples in two evaluators: one drops the temperature key from sampling_args; the other now yields None instead of a dict containing temperature. Updated a unit test to stop passing temperature=0 and removed related comments. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Pre-merge checks and finishing touches❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✨ Finishing touches
🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal). Please share your feedback with us on this Discord post. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
This is a follow-up to a comment on #7294. Apparently, the changes made to some tests in #7294 are no longer required and hence reverted here.
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)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
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
/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...
Provide a user friendly way for developers to interact with a Jenkins server.
Run
/bot [-h|--help]
to print this help message.See details below for each supported subcommand.
run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]
Launch build/test pipelines. All previously running jobs will be killed.
--reuse-test (optional)pipeline-id
(OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.--disable-reuse-test
(OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.--disable-fail-fast
(OPTIONAL) : Disable fail fast on build/tests/infra failures.--skip-test
(OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.--stage-list "A10-PyTorch-1, xxx"
(OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.--gpu-type "A30, H100_PCIe"
(OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.--test-backend "pytorch, cpp"
(OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.--only-multi-gpu-test
(OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.--disable-multi-gpu-test
(OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.--add-multi-gpu-test
(OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.--post-merge
(OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx"
(OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".--detailed-log
(OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.--debug
(OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in thestage-list
parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.For guidance on mapping tests to stage names, see
docs/source/reference/ci-overview.md
and the
scripts/test_to_stage_mapping.py
helper.kill
kill
Kill all running builds associated with pull request.
skip
skip --comment COMMENT
Skip testing for latest commit on pull request.
--comment "Reason for skipping build/test"
is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.reuse-pipeline
reuse-pipeline
Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.