-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[None][feat] AutoDeploy: Nemotron-H accuracy test #8133
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 |
1 similar comment
|
/bot run |
|
PR_Github #20595 [ run ] triggered by Bot |
📝 WalkthroughWalkthroughAdds a new integration accuracy test class for Nemotron-H-8B-Base-8K, including default kwargs and sampling params, and an end-to-end auto-dtype evaluation covering MMLU and GSM8K. Updates imports to include GSM8K. Applies minor formatting tweaks and small non-functional logic reflow within the same test module. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant T as TestNemotronH
participant H as LlmapiAccuracyTestHarness
participant E as Eval Runner
participant D1 as Dataset: MMLU
participant D2 as Dataset: GSM8K
Note over T: test_auto_dtype()
T->>T: get_default_kwargs()
T->>T: get_default_sampling_params()
T->>H: run_eval(model="Nemotron-H-8B-Base-8K", kwargs, sampling)
H->>E: evaluate(model, MMLU, sampling/kwargs)
E->>D1: load/supply items
E-->>H: results (MMLU)
H->>E: evaluate(model, GSM8K, defaults)
E->>D2: load/supply items
E-->>H: results (GSM8K)
H-->>T: aggregated results
Note over T: Assertions complete
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Pre-merge checks and finishing touches❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
tests/integration/defs/accuracy/test_llm_api_autodeploy.py (2)
78-81: Consider adding hub ID fallback for consistency.Unlike
TestLlama3_1_8B(line 42),MODEL_PATHlacks a fallback to a HuggingFace hub ID. Ifllm_models_root()returnsNoneor the path doesn't exist, this will fail rather than falling back to the hub.Consider applying this pattern for consistency:
- MODEL_PATH = f"{llm_models_root()}/Nemotron-H-8B-Base-8K" + MODEL_PATH = _hf_model_dir_or_hub_id("Nemotron-H-8B-Base-8K", MODEL_NAME)
86-86: Clarify "PyTorch test" reference.The comment mentions "PyTorch test," but this is an AutoDeploy test. Please clarify whether this refers to a different test suite or if the comment should be updated.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
tests/integration/defs/accuracy/test_llm_api_autodeploy.py(2 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{h,hpp,hh,hxx,cpp,cxx,cc,cu,cuh,py}
📄 CodeRabbit inference engine (CODING_GUIDELINES.md)
Use only spaces, no tabs; indent with 4 spaces.
Files:
tests/integration/defs/accuracy/test_llm_api_autodeploy.py
**/*.py
📄 CodeRabbit inference engine (CODING_GUIDELINES.md)
**/*.py: Python code must target Python 3.8+.
Indent Python code with 4 spaces; do not use tabs.
Maintain module namespace when importing; prefer 'from package.subpackage import foo' then 'foo.SomeClass()' instead of importing the class directly.
Python filenames should be snake_case (e.g., some_file.py).
Python classes use PascalCase names.
Functions and methods use snake_case names.
Local variables use snake_case; prefix 'k' for variables that start with a number (e.g., k_99th_percentile).
Global variables use upper SNAKE_CASE prefixed with 'G' (e.g., G_MY_GLOBAL).
Constants use upper SNAKE_CASE (e.g., MY_CONSTANT).
Avoid shadowing variables from an outer scope.
Initialize all externally visible members of a class in the constructor.
Prefer docstrings for interfaces that may be used outside a file; comments for in-function or file-local interfaces.
Use Google-style docstrings for classes and functions (Sphinx-parsable).
Document attributes and variables inline so they render under the class/function docstring.
Avoid reflection when a simpler, explicit approach suffices (e.g., avoid dict(**locals()) patterns).
In try/except, catch the most specific exceptions possible.
For duck-typing try/except, keep the try body minimal and use else for the main logic.
Files:
tests/integration/defs/accuracy/test_llm_api_autodeploy.py
**/*.{cpp,cxx,cc,h,hpp,hh,hxx,cu,cuh,py}
📄 CodeRabbit inference engine (CODING_GUIDELINES.md)
Prepend the NVIDIA Apache-2.0 copyright header with current year to the top of all source files (e.g., .cpp, .h, .cu, .py).
Files:
tests/integration/defs/accuracy/test_llm_api_autodeploy.py
🧬 Code graph analysis (1)
tests/integration/defs/accuracy/test_llm_api_autodeploy.py (1)
tests/integration/defs/accuracy/accuracy_core.py (6)
GSM8K(332-347)MMLU(315-329)CnnDailymail(248-265)LlmapiAccuracyTestHarness(844-855)evaluate(184-245)evaluate(763-773)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Pre-commit Check
🔇 Additional comments (6)
tests/integration/defs/accuracy/test_llm_api_autodeploy.py (6)
1-14: LGTM!The copyright header is correctly formatted with the current year (2025) and follows the required NVIDIA Apache-2.0 format.
24-24: LGTM!The GSM8K import is necessary for the new test class and follows the module namespace import guidelines.
27-37: LGTM!The walrus operator refactor is concise and preserves the original logic while remaining compatible with Python 3.8+.
40-76: LGTM!The formatting improvements enhance readability and maintain consistency with the rest of the file. No functional changes detected.
105-113: LGTM!The test structure is correct. MMLU uses custom sampling params (appropriate for multiple-choice tasks), while GSM8K uses defaults (appropriate for longer generative outputs). The memory requirement and model/tokenizer setup follow established patterns.
98-103: Verify Nemotron Model EOS Token ID
The EOS ID is currently hardcoded to-1, matching Llama defaults, but Nemotron-H-8B-Base-8K may use a different value. Confirmtokenizer.eos_token_id(ormodel.config.eos_token_id) for this model equals-1and update the hardcoded value if needed.
|
PR_Github #20596 [ run ] triggered by Bot |
|
PR_Github #20595 [ run ] completed with state |
|
PR_Github #20596 [ run ] completed with state |
Signed-off-by: Lucas Liebenwein <11156568+lucaslie@users.noreply.github.com>
9690853 to
5645862
Compare
|
/bot run |
|
PR_Github #20600 [ run ] triggered by Bot |
|
/bot run --disable-fail-fast |
|
PR_Github #20609 [ run ] triggered by Bot |
|
PR_Github #20600 [ run ] completed with state |
Signed-off-by: Lucas Liebenwein <11156568+lucaslie@users.noreply.github.com>
|
/bot run |
|
PR_Github #20612 [ run ] triggered by Bot |
|
PR_Github #20609 [ run ] completed with state |
|
PR_Github #20612 [ run ] completed with state |
Summary by CodeRabbit
Tests
Style
Chores
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)
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-listparameter 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.mdand the
scripts/test_to_stage_mapping.pyhelper.kill
killKill all running builds associated with pull request.
skip
skip --comment COMMENTSkip 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-pipelineReuse 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.