[CI][CUDA][B200][Smoke Test] Add one more B200 smoke test. Change periodic frequency from every 6 hours to every 2 hours

[nWEIdia]

Fix low utilization issue for linux.dgx.b200.
linux.dgx.b200.8 is much busier.
According to https://hud.pytorch.org/runners/pytorch?search=dgx.b200

cc @drisspg @malfet @eqy @tinglvv @ptrblck @atalman @huydhn

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

❌ 1 New Failure, 26 Pending

As of commit c175821 with merge base c055ebe ():

NEW FAILURE - The following job has failed:

• B200 Smoke Tests / linux-jammy-cuda12.8-py3.10-gcc11-sm100 / test (smoke_b200, 1, 1, linux.dgx.b200) (gh)
  test/inductor/test_torchinductor.py::GPUTests::test_weight_norm_conv2d_cuda

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

[nWEIdia]

@pytorchbot merge -f "Unlikely to cause regressions. I will create an issue for the red signals and fix later. These issues are not blocking other PRs."

[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