[serge] integration failure triage - 2026-06-28
Author: github-actions[bot]
Pull request: no

<!-- serge-triage-run:integration-failure-triage:2026-06-28 -->

Automated **integration-failure triage** for the daily CI window `2026-06-22 → 2026-06-28`.

This issue was generated by AI-assisted automation. The grouping, summaries, and recommended follow-up can be incomplete or misleading; verify the failures before acting.

Serge dispatched one task per failure group below — each opens or updates its own PR on a `serge/fix/itf-<fingerprint>` branch. This table is refreshed in place as Serge opens PRs during the run; a group still showing `(pending)` either had no safe fix or is still running, and gets linked on the next nightly run if its PR appears later.

## Dispatched failure groups

| Model | Error | Occurrences | PR |
| --- | --- | --- | --- |
| `whisper` | other — other (20), shape/size mismatch (2) | 22 | #46949 |
| `whisper` | output_mismatch — list output differs (10), other (6), tensor values differ (4) | 20 | `serge/fix/itf-5fadcce436e9` (pending) |
| `musicgen_melody` | output_mismatch — tensor values differ (16) | 16 | `serge/fix/itf-f92dbb6ad177` (pending) |
| `gemma` | output_mismatch — list output differs (14) | 14 | `serge/fix/itf-94e6520abd4c` (pending) |
| `dac` | output_mismatch — tensor values differ (6), other (6) | 12 | #46941 |
| `edgetam` | import_or_config — other (12) | 12 | #46907 |
| `glm46v` | other — other (12) | 12 | #46927 |
| `minimax_m3_vl` | load_error — other (12) | 12 | #46926 |
| `gemma3` | output_mismatch — list output differs (8), other (2) | 10 | `serge/fix/itf-60705cb0b3f3` (pending) |
| `gemma3n` | output_mismatch — list output differs (10) | 10 | `serge/fix/itf-0498ca54f373` (pending) |
| `glm_ocr` | output_mismatch — list output differs (10) | 10 | `serge/fix/itf-aa4efdb4f52e` (pending) |
| `deepseek_v32` | load_error — other (8) | 8 | #46908 |
| `falcon_mamba` | output_mismatch — other (6), list output differs (2) | 8 | `serge/fix/itf-f87e290c2bd6` (pending) |
| `generation` | output_mismatch — list output differs (4), other (4) | 8 | `serge/fix/itf-db92e334b637` (pending) |
| `grounding_dino` | output_mismatch — tensor values differ (6), other (2) | 8 | `serge/fix/itf-05605f829482` (pending) |
| `higgs_audio_v2` | output_mismatch — tensor values differ (8) | 8 | `serge/fix/itf-8ce58bb033f0` (pending) |
| `mamba2` | OOM — other (8) | 8 | `serge/fix/itf-b05c963d2c22` (pending) |
| `mllama` | output_mismatch — other (8) | 8 | `serge/fix/itf-a29b4efa9538` (pending) |
| `mpt` | other — other (8) | 8 | `serge/fix/itf-f6af7ce18da4` (pending) |
| `peft_integration` | other — other (8) | 8 | `serge/fix/itf-3d095811de43` (pending) |

_Generated 2026-06-29T00:39:39+00:00._

Comments:
the part that quietly loses signal here is the `(pending)` bucket fusing two opposite outcomes: 'no safe fix existed' (terminal, wants a human) and 'still running' (transient, resolves itself). both render identically in the table, and 'gets linked on the next nightly run if its PR appears later' means the no-fix groups just roll forward looking in-flight forever. nobody gets paged for the ones serge quietly gave up on, because the status that means 'i failed' is the same one that means 'wait.'