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

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

**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-08-07 · **Last seen:** 2026-08-07

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| qnx-integration | 1 | 100 |

```json
{
"configs": {
"qnx-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 1,
"cumulative_total_runs": 100,
"first_seen": "2026-08-07",
"last_seen": "2026-08-07",
"nightly_count": 1,
"target": "//score/mw/com/test/methods/mixed_criticality/integration_test:asilb_consumer_qm_provider_test"
}
```

Start with the Bazel target //score/mw/com/test/methods/mixed_criticality/integration_test:asilb_consumer_qm_provider_test and run it under the qnx-integration configuration, repeating it enough to observe the failure. Inspect the test and its mixed-criticality integration dependencies to identify the nondeterminism; done means the test no longer flakes in repeated runs.

Written by the indexing model from the issue text.