Skip to content

Comments

[None][fix] Fix silent MPI failures on models with custom tokenizers#11399

Merged
pcastonguay merged 3 commits intoNVIDIA:mainfrom
jthomson04:jthomson04/fix-kimi-multinode
Feb 18, 2026
Merged

[None][fix] Fix silent MPI failures on models with custom tokenizers#11399
pcastonguay merged 3 commits intoNVIDIA:mainfrom
jthomson04:jthomson04/fix-kimi-multinode

Conversation

@jthomson04
Copy link
Collaborator

@jthomson04 jthomson04 commented Feb 10, 2026

Multi-node MPI serving hangs on startup for trust_remote_code=True models (e.g. Kimi K2). The tokenizer is pickled into the MPI payload, but remote workers can't deserialize it because the dynamic transformers_modules namespace doesn't exist on their side. The workers fail silently, and the remaining ranks hang at an MPI barrier.

To fix this, we strip the tokenizer from the MPI payload (proxy.py), and reload it if needed for guided decoding. I also added some logging to prevent these sorts of silent failures.

Summary by CodeRabbit

Release Notes

  • Bug Fixes

    • Resolved tokenizer serialization failures in MPI distributed execution environments
    • Enhanced error tracking and logging in MPI session management for improved diagnostics
  • Improvements

    • Guided decoding now automatically loads tokenizer from checkpoint when not explicitly provided

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

  • 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

/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.

Details

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 the stage-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.

@jthomson04 jthomson04 requested review from a team as code owners February 10, 2026 01:18
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 10, 2026

📝 Walkthrough

Walkthrough

These changes implement lazy tokenizer loading for guided decoding, filter tokenizer arguments from MPI worker submissions to prevent serialization failures, and enhance error tracking in the MPI session server with improved failure logging and iteration over futures as they complete.

Changes

Cohort / File(s) Summary
Guided Decoding Tokenizer Support
tensorrt_llm/_torch/pyexecutor/py_executor_creator.py
Adds lazy tokenizer loading from checkpoint directory when guided decoding is requested but no tokenizer is provided. Constructs guided decoding config using the loaded TransformersTokenizer at runtime.
MPI Worker & Session Improvements
tensorrt_llm/executor/proxy.py, tensorrt_llm/llmapi/mpi_session.py
Filters tokenizer argument from MPI worker kwargs to avoid pickle failures on remote nodes; enhances error handling in session server by iterating over futures as they complete, tracking failed futures, logging individual failure details, and providing summary failure information.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2
❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning PR description explains the issue and solution clearly, but critical sections from the template (PR title, Test Coverage, and PR Checklist items) are missing or incomplete. Add a proper PR title following the template format (e.g., '[TRTLLM-XXXX][fix] Fix silent MPI failures...'). Complete the Test Coverage section by listing relevant tests. Review all PR Checklist items systematically.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title '[None][fix] Fix silent MPI failures on models with custom tokenizers' clearly and specifically summarizes the main fix being implemented in the pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@jthomson04
Copy link
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35389 [ run ] triggered by Bot. Commit: b8f7ce4

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35389 [ run ] completed with state ABORTED. Commit: b8f7ce4
LLM/main/L0_MergeRequest_PR #27335 (Blue Ocean) completed with status: ABORTED

@jthomson04
Copy link
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35409 [ run ] triggered by Bot. Commit: b8f7ce4

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35409 [ run ] completed with state SUCCESS. Commit: b8f7ce4
/LLM/main/L0_MergeRequest_PR pipeline #27349 completed with status: 'FAILURE'

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

@jthomson04 jthomson04 requested a review from a team as a code owner February 10, 2026 17:26
@jthomson04 jthomson04 requested a review from Fridah-nv February 10, 2026 17:26
@jthomson04
Copy link
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35524 [ run ] triggered by Bot. Commit: cbf76a5

Copy link
Collaborator

@Fridah-nv Fridah-nv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AutoDeploy change LGTM

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35524 [ run ] completed with state SUCCESS. Commit: cbf76a5
/LLM/main/L0_MergeRequest_PR pipeline #27429 completed with status: 'FAILURE'

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

@jthomson04 jthomson04 force-pushed the jthomson04/fix-kimi-multinode branch from cbf76a5 to 4191347 Compare February 11, 2026 00:50
@jthomson04
Copy link
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35556 [ run ] triggered by Bot. Commit: 4191347

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35556 [ run ] completed with state SUCCESS. Commit: 4191347
/LLM/main/L0_MergeRequest_PR pipeline #27460 completed with status: 'FAILURE'

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

Signed-off-by: jthomson04 <jwillthomson19@gmail.com>
Signed-off-by: jthomson04 <jwillthomson19@gmail.com>
Signed-off-by: jthomson04 <jwillthomson19@gmail.com>
@jthomson04 jthomson04 force-pushed the jthomson04/fix-kimi-multinode branch from 4191347 to c95d03b Compare February 12, 2026 00:31
@jthomson04
Copy link
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35687 [ run ] triggered by Bot. Commit: c95d03b

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35687 [ run ] completed with state SUCCESS. Commit: c95d03b
/LLM/main/L0_MergeRequest_PR pipeline #27564 completed with status: 'FAILURE'

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

@pcastonguay
Copy link
Collaborator

/bot run --disable-fail-fast

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35788 [ run ] triggered by Bot. Commit: c95d03b

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35788 [ run ] completed with state SUCCESS. Commit: c95d03b
/LLM/main/L0_MergeRequest_PR pipeline #27639 completed with status: 'FAILURE'

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

@pcastonguay
Copy link
Collaborator

/bot skip --comment "Flaky multi-GPU test"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35806 [ skip ] triggered by Bot. Commit: c95d03b

@tensorrt-cicd
Copy link
Collaborator

PR_Github #35806 [ skip ] completed with state SUCCESS. Commit: c95d03b
Skipping testing for commit c95d03b

@pcastonguay pcastonguay merged commit 66861a0 into NVIDIA:main Feb 18, 2026
5 checks passed
brb-nv pushed a commit to brb-nv/TensorRT-LLM that referenced this pull request Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants