[CI] Skip test_Conv1d_zero_batch

[rraminen]

Skip the below unit test across all the archs for a cleaner run

external-builds/pytorch/pytorch/test/test_nn.py::TestNN::test_Conv1d_zero_batch

This test fails with a Segmentation fault (core dumped) error, which isn’t related to PyTorch and may be due to changes in the ROCm version. (https://github.com/ROCm/TheRock/actions/runs/25273411730/job/74102474492)

This test passed with torch==2.11.0+rocm7.13.0a20260430 (gfx94x) (APR 30) - https://github.com/ROCm/TheRock/actions/runs/25150366706/job/73730936029

First failure occured with torch==2.11.0+rocm7.13.0a20260502 (gfx94X) (MAY 2) - https://github.com/ROCm/TheRock/actions/runs/25312522580/job/74208101156

[ScottTodd]

If ROCm code is causing a segfault, that needs to get fixed. That's exactly what these tests are meant to exercise (pytorch is already tested against stable rocm releases upstream, here is where we test pytorch against latest rocm)

[pragupta]

@ScottTodd -- Yeah true, our builds were not getting promoted so this was just a desperate attempt to get us to green. But, yes, on a second thought, we should hold on these and wait for proper rocm fix to come in.

[ScottTodd]

Note that for multi-arch packages we're planning on removing the "promoted" concept entirely, since we haven't found a good way to make that work with the unified release index. See #5107. More reason to get tests passing :)

For segfaults though, we can blur the lines a bit... Windows tests for some torch versions in particular have been failing due to segfaults and that prevents getting clear test signal since the test runner crashes and does not run all expected tests.

In this case I'd like to see some triage performed and if we can identify a culprit for reverting quickly, especially if we already have a precise window where this regressed (April 30 - May 2).