Flaky test: //score/mw/com/test/methods/mixed_criticality/integration_test:qm_consumer_qm_provider_test

## Flaky test: `//score/mw/com/test/methods/mixed_criticality/integration_test:qm_consumer_qm_provider_test`

**Cumulative failed runs observed:** 3 (over 300 total runs, 3 nightlies)
**First seen:** 2026-08-04 · **Last seen:** 2026-08-18

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 3 | 300 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 3,
"total_runs": 300
}
},
"cumulative_failed_runs": 3,
"cumulative_total_runs": 300,
"first_seen": "2026-08-04",
"last_seen": "2026-08-18",
"nightly_count": 3,
"target": "//score/mw/com/test/methods/mixed_criticality/integration_test:qm_consumer_qm_provider_test"
}
```

Start with the //score/mw/com/test/methods/mixed_criticality/integration_test:qm_consumer_qm_provider_test target and run it under the gcc15-integration configuration. Review the three failed runs across the reported nightlies and identify the source of the flakiness. Done means the test no longer fails intermittently in subsequent runs.

Written by the indexing model from the issue text.