[Distributed tests] Add skip for odd world_size condition

[jaglinux]

As per #74995, the tests
needs to be skipped for odd WORLD_SIZE

Signed-off-by: Jagadish Krishnamoorthy [email protected]

Fixes #74995

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/76136
• 📄  Preview Python docs built from this PR
• 📄  Preview C++ docs built from this PR
• ❓Need help or want to give feedback on the CI? Visit our office hours

💊 CI failures summary and remediations

As of commit b17a5ce (more details on the Dr. CI page):

Expand to see more

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[jaglinux]

cc @jeffdaily @pruthvistony @KyleCZH @arindamroy-eng

[pytorch-bot]

We have recently simplified the CIFlow labels and ci/master is no longer in use.
You can use any of the following

• ciflow/trunk (.github/workflows/trunk.yml): all jobs we run per-commit on master
• ciflow/periodic (.github/workflows/periodic.yml): all jobs we run periodically on master
• ciflow/all: trunk + periodic; all jobs we run in master CI
• ciflow/android (.github/workflows/run_android_tests.yml): android build and test
• ciflow/nightly (.github/workflows/nightly.yml): all jobs we run nightly
• ciflow/binaries: all binary build and upload jobs
• ciflow/binaries_conda: binary build and upload job for conda
• ciflow/binaries_libtorch: binary build and upload job for libtorch
• ciflow/binaries_wheel: binary build and upload job for wheel

[mrshenli]

@pytorchbot merge this please

[pytorch-bot]

+1

[github-actions]

Hey @jaglinux.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.