[Gemma] Update expected values for A10G (#47976)
* [Gemma] Update expected values for A10G after PyTorch 2.9.0 upgrade
Update 7 failing Gemma integration tests to reflect output changes on
CUDA compute capability 8.x (A10G) after the PyTorch 2.8.0→2.9.0 upgrade
in the CI Docker image (`10d557123b`):
- test_model_2b_4bit: add ("cuda", 8) key with new brush output
- test_model_7b_fp16: add ("cuda", 8) key with "1995 4.0L 4x4" output
- test_model_7b_bf16: update ("cuda", 8) key[0] to "small game" output
- test_model_7b_fp16_static_cache: update ("cuda", 8) to "1999 4.0L 4x4"
- test_model_7b_4bit: update ("cuda", 8) with new quantization outputs
- test_compile_static_cache: add ("cuda", 8) key with "110bhp" variant
- test_export_static_cache: remove stale ("cuda", 8) key (A10G now matches (None, None))
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [Gemma] Fix test_model_7b_fp16_static_cache ("cuda", 8) expected value
Update second element to "DIY mini-f" which is the output produced on a
fresh CUDA context (as in CI). "DIY 3D" is produced on warm CUDA contexts
(repeated SSH runs) due to different memory allocation and SDPA kernel
selection on first vs subsequent process invocations.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Revert "[Gemma] Fix test_model_7b_fp16_static_cache ("cuda", 8) expected value"
This reverts commit cf17b840d3722590124ca84662f25ee49c1a21e7.
* [Gemma] Truncate flaky suffix in test_model_7b_fp16_static_cache
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [Gemma] Fix test_compile_static_cache: compile __call__ instead of forward
Compiling model.forward causes a CUDA graph tree RuntimeError on
PyTorch >= 2.9 when multiple generate() calls are made on the same
model instance. Using model.__call__ (matching the Mistral test pattern)
avoids the CUDA graph lifecycle conflict.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: ydshieh <ydshieh@users.noreply.github.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
