-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[None][infra] Let CI continue running other isolation tests when an isolation test get hanging #8471
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
📝 WalkthroughWalkthroughPytest timeout reduced from 3600 to 500 seconds in CI pipeline. Test file modified with intentional failure and 6-minute delay for debugging purposes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Pre-merge checks and finishing touches❌ Failed checks (2 warnings, 1 inconclusive)
✨ 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: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
tests/integration/defs/triton_server/test_triton.py (2)
237-245: Critical: Remove intentional test failure before merging.This
pytest.fail("emma test for hang")will cause the test to always fail and prevents the actual test logic from executing. This appears to be temporary debug code for investigating hang issues and must be removed before merging to main.Apply this diff to remove the debug code:
@pytest.mark.parametrize("test_name", ["gpt-2b-ib-lora"], indirect=True) def test_gpt_2b_ib_lora(tritonserver_test_root, test_name, llm_root, model_path, engine_dir): - pytest.fail("emma test for hang") build_model(test_name, llm_root, tritonserver_test_root) tokenizer_type = "auto" run_shell_command(
407-416: Critical: Remove 6-minute debug delay before merging.The
time.sleep(6 * 60)introduces a 6-minute delay that will significantly slow down the CI pipeline. With the pytest timeout reduced to 500 seconds (8.3 minutes) in the related Groovy change, this sleep consumes 72% of the available timeout window. This appears to be temporary debug code for testing timeout behavior and must be removed before merging.Apply this diff to remove the debug delay:
@pytest.mark.parametrize("test_name", ["llava"], indirect=True) def test_llava(tritonserver_test_root, test_name, llm_root, model_path, engine_dir): - time.sleep(6 * 60) build_model(test_name, llm_root, tritonserver_test_root) tokenizer_type = "auto" visual_encoder_path = f"{llm_root}/examples/models/core/multimodal/tmp/trt_engines/llava-1.5-7b-hf/multimodal_encoder/"
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
jenkins/L0_Test.groovy(1 hunks)tests/integration/defs/triton_server/test_triton.py(3 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/triton_server/test_triton.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/triton_server/test_triton.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/triton_server/test_triton.py
⏰ 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 (1)
jenkins/L0_Test.groovy (1)
1997-1997: Clarify whether 500-second timeout reduction is correct for this stage or requires verification.The verification confirms the 6-minute sleep exists in
test_llavabut contradicts the review comment's assumption that it's a debug change—the sleep is not marked as temporary or debug anywhere in the code. However, the codebase shows two differentpytestTestTimeoutvalues in the same file: 7200 seconds at line 767 and 500 seconds at line 1997, indicating different stages have intentionally different timeouts.The 500-second timeout leaves only ~140 seconds for test logic after the 360-second sleep, which may be intentional for this specific stage. Without understanding the purpose of this particular stage or seeing the full diff context, it's unclear whether this value is correct or needs adjustment.
|
/bot run --stage-list "B200_PCIe-Triton-Post-Merge-1" |
|
PR_Github #21754 [ run ] triggered by Bot. Commit: |
|
PR_Github #21754 [ run ] completed with state |
|
/bot run --stage-list "B200_PCIe-Triton-Post-Merge-1" |
|
PR_Github #21757 [ run ] triggered by Bot. Commit: |
|
PR_Github #21757 [ run ] completed with state |
|
/bot run --stage-list "B200_PCIe-Triton-Post-Merge-1" |
|
PR_Github #21762 [ run ] triggered by Bot. Commit: |
|
PR_Github #21762 [ run ] completed with state |
|
/bot run --stage-list "B200_PCIe-Triton-Post-Merge-1" |
|
PR_Github #21765 [ run ] triggered by Bot. Commit: |
|
PR_Github #21765 [ run ] completed with state |
|
/bot run --stage-list "[DGX_H100-4_GPUs-CPP-1]" |
|
/bot run --stage-list "DGX_H100-4_GPUs-CPP-1" |
|
PR_Github #21870 [ run ] triggered by Bot. Commit: |
|
PR_Github #21871 [ ] completed with state |
|
PR_Github #21870 [ run ] completed with state |
|
/bot run --stage-list "DGX_H100-4_GPUs-CPP-1" |
1 similar comment
|
/bot run --stage-list "DGX_H100-4_GPUs-CPP-1" |
|
PR_Github #21873 [ run ] triggered by Bot. Commit: |
Signed-off-by: qqiao <[email protected]>
Signed-off-by: qqiao <[email protected]>
Signed-off-by: qqiao <[email protected]>
Signed-off-by: qqiao <[email protected]>
Co-authored-by: Yanchao Lu <[email protected]> Signed-off-by: Emma Qiao <[email protected]>
98e059e to
874ea8c
Compare
Signed-off-by: qqiao <[email protected]>
|
/bot run |
|
PR_Github #21921 [ run ] triggered by Bot. Commit: |
|
PR_Github #21921 [ run ] completed with state |
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.
LGTM
Signed-off-by: Emma Qiao <[email protected]>
|
/bot run --stage-list "DGX_H100-4_GPUs-CPP-1" |
|
PR_Github #21981 [ run ] triggered by Bot. Commit: |
|
PR_Github #21981 [ run ] completed with state |
|
/bot run |
|
PR_Github #22013 [ run ] triggered by Bot. Commit: |
|
PR_Github #22013 [ run ] completed with state |
|
/bot run |
|
PR_Github #22044 [ run ] triggered by Bot. Commit: |
|
PR_Github #22044 [ run ] completed with state |
…solation test get hanging (NVIDIA#8471) Signed-off-by: qqiao <[email protected]> Signed-off-by: Emma Qiao <[email protected]> Co-authored-by: Yanchao Lu <[email protected]> Signed-off-by: yufeiwu-nv <[email protected]>
…solation test get hanging (NVIDIA#8471) Signed-off-by: qqiao <[email protected]> Signed-off-by: Emma Qiao <[email protected]> Co-authored-by: Yanchao Lu <[email protected]>
…solation test get hanging (NVIDIA#8471) Signed-off-by: qqiao <[email protected]> Signed-off-by: Emma Qiao <[email protected]> Co-authored-by: Yanchao Lu <[email protected]>
…solation test get hanging (NVIDIA#8471) Signed-off-by: qqiao <[email protected]> Signed-off-by: Emma Qiao <[email protected]> Co-authored-by: Yanchao Lu <[email protected]>
…solation test get hanging (NVIDIA#8471) Signed-off-by: qqiao <[email protected]> Signed-off-by: Emma Qiao <[email protected]> Co-authored-by: Yanchao Lu <[email protected]>
Summary by CodeRabbit
Note: These changes are internal test infrastructure modifications with no direct impact on end-user functionality.
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.