[ez] Serial when NUM_PROCS is 1

[clee2000]

Makes it easier to understand whats going on

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/117977

• 📄 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 the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (2 Unrelated Failures)

As of commit 231be70 with merge base 3c1498d ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• slow / linux-focal-cuda12.1-py3-gcc9-slow-gradcheck / test (default, 4, 4, linux.g5.4xlarge.nvidia.gpu) (gh)
  test_modules.py::TestModuleCUDA::test_gradgrad_nn_GroupNorm_cuda_float64

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

• pull / linux-focal-py3_8-clang9-xla / test (xla, 1, 1, linux.12xlarge, unstable) (gh)
  Process completed with exit code 128.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[huydhn]

LGTM! May be you also want to print the logs directly to stdout instead of file, but I guess that doesn't really matter as no one is looking that the log output interactively

[clee2000]

LGTM! May be you also want to print the logs directly to stdout instead of file, but I guess that doesn't really matter as no one is looking that the log output interactively

I think the logs would end up super long again if that happened, the benefit of piping to file is both preventing interleaving and also reducing the job log size

[clee2000]

@pytorchbot merge -f "no trunk needed"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here