Skip fp16-config tests on accelerators without fp16 support (#8398)
## Problem
`TestMultipleModels::test_zero_optimizer`, `TestSimpleMoE`, `TestMoE`,
`TestPRMoE`, and `TestMOETensorParallel` hardcode `"fp16": {"enabled":
True}` in their DeepSpeed configs. The engine's sanity check then
raises:
```
ValueError: Type fp16 is not supported on your device.
```
on any accelerator whose `is_fp16_supported()` is false. On CPU that
maps to the AVX512-FP16 capability of the host, and GitHub's
`ubuntu-24.04` runners are hardware-heterogeneous: **the same test
passes on one runner and fails on the next** (observed directly in #8381
— 146 failures appeared on one runner generation and none on another,
with identical code).
## Change
Skip these tests via a capability query:
```python
@pytest.mark.skipif(not get_accelerator().is_fp16_supported(), reason="fp16 is not supported on this accelerator")
```
- capability only, no accelerator-name matching;
- mirrors the existing bf16 skip precedent in
`tests/unit/v1/zero/test_zero_user_backward.py`;
- deliberately a **skip** rather than silently running bf16 — these
tests exist to cover the fp16 paths.
## Validation
Validated as part of the multi-rank CPU CI experiment in #8381: the 146
hardware-lottery failures became deterministic skips, zero regressions
on previously-passing tests.
Signed-off-by: Guokai Ma <guokai.ma@intel.com>
DeepSpeed
493dafa0 - Skip fp16-config tests on accelerators without fp16 support (#8398)
