CI: update multi gpu test trigger file list

[QiJune]

Summary by CodeRabbit

• Chores
  • Updated the criteria for triggering multi-GPU testing to include additional relevant files.

[coderabbitai]

Walkthrough

The change updates the getMultiGpuFileChanged function in the Jenkins pipeline script to include two additional C++ source files related to multi-GPU operations. This ensures that changes to these files will now trigger multi-GPU testing during the CI process. No other logic or function signatures were altered.

Changes

File(s)	Change Summary
jenkins/L0_MergeRequest.groovy	Added two file paths to the list of files that trigger multi-GPU tests in CI.

Poem

Two files join the multi-GPU crew,
Ensuring tests know what to do.
With allgather and reducescatter in the mix,
The CI pipeline gets new tricks.
🐇 Hopping forward, code in sync—
More robust checks in just a blink!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d4d21a1 and 67e5e9f.

📒 Files selected for processing (1)

• jenkins/L0_MergeRequest.groovy (1 hunks)

🔇 Additional comments (1)

jenkins/L0_MergeRequest.groovy (1)

568-569: LGTM! Correctly adds multi-GPU related files to trigger list.

The addition of allgatherOp.cpp and reducescatterOp.cpp is appropriate as these files implement collective communication operations that are essential for multi-GPU functionality. This ensures that changes to these files will properly trigger multi-GPU testing in the CI pipeline.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[QiJune]

/bot skip --comment "trivial changes"

[tensorrt-cicd]

PR_Github #12166 [ skip ] triggered by Bot

[tensorrt-cicd]

PR_Github #12166 [ skip ] completed with state SUCCESS
Skipping testing for commit 67e5e9f