[None][fix] Pin Ray version to 2.54.1

[shuyixiong]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated test infrastructure dependencies to ensure consistent test environment stability.

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

To see a list of available CI bot commands, please comment /bot help.

[coderabbitai]

📝 Walkthrough

Walkthrough

A single line in the Groovy build script was modified to pin the Ray dependency to version 2.54.1 in the Ray-specific test stage. The installation command now includes an explicit version constraint instead of allowing any version of the ray[default] package.

Changes

Cohort / File(s)	Summary
Ray Dependency Pinning jenkins/L0_Test.groovy	Modified Ray package installation to pin version 2.54.1 in the Ray-specific stage within runLLMTestlistOnPlatformImpl function.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is empty with no explanation of the issue, rationale, or test coverage details provided by the author.	Fill in the Description section explaining why Ray needs to be pinned to 2.54.1, document relevant test coverage, and complete the PR checklist appropriately.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title '[None][fix] Pin Ray version to 2.54.1' is fully related to the main change, clearly summarizing the pinning of Ray to a specific version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[shuyixiong]

/bot run --stage-list "H100_PCIe-PyTorch-Ray-1"

[tensorrt-cicd]

PR_Github #43428 [ run ] triggered by Bot. Commit: 4c6c6e7 Link to invocation

[tensorrt-cicd]

PR_Github #43428 [ run ] completed with state SUCCESS. Commit: 4c6c6e7
/LLM/main/L0_MergeRequest_PR pipeline #33960 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[shuyixiong]

/bot skip --comment "Just pin the Ray version to 2.54.1, which has a passing Ray stage."

[tensorrt-cicd]

PR_Github #43475 [ skip ] triggered by Bot. Commit: 4c6c6e7 Link to invocation

[tensorrt-cicd]

PR_Github #43475 [ skip ] completed with state SUCCESS. Commit: 4c6c6e7
Skipping testing for commit 4c6c6e7

Link to invocation