[None][fix] Pin Ray version to 2.54.1 in slurm CI stage

[shuyixiong]

Summary by CodeRabbit

• Chores
  • Pinned a dependency version to ensure stable and consistent build environments during testing.

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 14403d44-e945-447b-9f94-ca9cf9e8ea90

📥 Commits

Reviewing files that changed from the base of the PR and between 67fde60 and 444f212.

📒 Files selected for processing (1)

• jenkins/scripts/slurm_install.sh

---

📝 Walkthrough

Walkthrough

Updated the Ray installation command in jenkins/scripts/slurm_install.sh to pin the ray[default] dependency to exact version 2.54.1 when the pytest command includes --run-ray* flags, changing from an unversioned to versioned dependency specification.

Changes

Cohort / File(s)	Summary
Ray Dependency Pinning jenkins/scripts/slurm_install.sh	Pinned ray[default] to exact version 2.54.1 in the conditional Ray installation step within the slurm_install_setup() function.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [None][fix] Pin Ray version to 2.54.1 #13071 — Also pins ray[default] to version 2.54.1 in a separate CI script (jenkins/L0_Test.groovy), indicating coordinated version management across CI workflows.

Suggested reviewers

• yuanjingx87
• venkywonka

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is entirely composed of the template with no actual content provided in the Description, Test Coverage, or explanatory sections.	Fill in the Description section explaining why Ray version needs to be pinned, and provide Test Coverage details showing how the change is validated.
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.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly specifies the main change: pinning Ray version to 2.54.1 in the slurm CI stage, which directly matches the changeset modifications.

_{✏️ 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 skip --comment "Pin Ray version to 2.54.1 in slurm CI stage"

[tensorrt-cicd]

PR_Github #43519 [ skip ] triggered by Bot. Commit: 5dafccf Link to invocation

[tensorrt-cicd]

PR_Github #43519 [ skip ] completed with state SUCCESS. Commit: 5dafccf
Skipping testing for commit 5dafccf

Link to invocation

[brb-nv]

LGTM.