[ROCm] Enable buffer_callback_test_gpu in ROCm CI
The exclusion claimed buffer_callback_test_gpu "uses py_import deps that
are incompatible with pre-built plugin wheels (build_jaxlib=false)". That
does not reproduce. The target was originally swept into the 45-target
blanket TESTS_TO_IGNORE list added by ce621cf53a ("[ROCm] Include
prebuilt rocm plugin pkgs as deps to tests"), and it was one of only two
entries left behind when db2242f82f dropped the other 43 as stale; the
stated reason was never verified against a real run.
Verified on gfx942 in ghcr.io/rocm/jax-base-ubu24.therock-7.14, using the
exact CI configuration -- --config=rocm_clang_hermetic --config=single_gpu
with --//jax:build_jaxlib=false --//jax:build_jax=false and the prebuilt
jax_rocm7_plugin/jax_rocm7_pjrt wheels staged in dist/ (the same wheels
the CI download action stages, which is where the rocm_wheels repo rule
picks them up):
51 cases: 23 pass, 28 skipped, 0 failures
5/5 consecutive runs pass, avg 3.5s, no teardown hang
The 28 skips are @jtu.run_on_devices("cpu") cases that are CPU-only by
design and skip identically on CUDA. The 23 that run are the 22
test_cuda_array_interface cases (11 dtypes x command_buffer_compatible)
plus test_side_effect, so this adds real coverage of the
__cuda_array_interface__ import path on ROCm.
Brings the single-GPU suite to 148 targets. The blocking PR gate is
unchanged at 1 target.
Also corrects the comment on the remaining exclusion. ops_test_mgpu_gpu
is a Mosaic GPU test, not a multi-accelerator one, and it carries no
multiaccelerator tag -- verified by query -- so the claim that it is
"excluded from single_gpu runs anyway" was wrong: the explicit exclusion
is the only thing keeping it out.
