fix: only set _mpi_session if world_size is > 1

[achartier]

PR title

fix: only set _mpi_session if world_size is > 1

Description

Only set _mpi_session if world_size is > 1

Test Coverage

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 [--disable-fail-fast --skip-test --stage-list "A10-1, xxx" --gpu-type "A30, H100_PCIe" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-[Post-Merge]-1, xxx"]

Launch build/test pipelines. All previously running jobs will be killed.

--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-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-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.

--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. Will also run 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-[Post-Merge]-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-[Post-Merge]-1, xxx".

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md.

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.

[achartier]

/bot run

[tensorrt-cicd]

PR_Github #9057 [ run ] triggered by Bot

[pcastonguay]

Do we have tests that cover both cases: multi-gpu single node, multi-gpu multi-nodes? Since this was missed in the first MR, I suspect we don't. Could we add such tests?

[tensorrt-cicd]

PR_Github #9057 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #6621 completed with status: 'FAILURE'

[achartier]

Do we have tests that cover both cases: multi-gpu single node, multi-gpu multi-nodes? Since this was missed in the first MR, I suspect we don't. Could we add such tests?

No, we don't have either config yet. We can add a single node one in CI and I started discussion with QA to add a multi-node test. Should it block this PR though?

[pcastonguay]

Do we have tests that cover both cases: multi-gpu single node, multi-gpu multi-nodes? Since this was missed in the first MR, I suspect we don't. Could we add such tests?

No, we don't have either config yet. We can add a single node one in CI and I started discussion with QA to add a multi-node test. Should it block this PR though?

Not having tests is not ideal but we can merge this for one to avoid more issues.

[achartier]

/bot run

[tensorrt-cicd]

PR_Github #9215 [ run ] triggered by Bot

[achartier]

/bot run

[tensorrt-cicd]

PR_Github #9238 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #9238 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #6774 completed with status: 'SUCCESS'