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

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

**Cumulative failed runs observed:** 4 (over 400 total runs, 4 nightlies)
**First seen:** 2026-08-15 · **Last seen:** 2026-09-09

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 4 | 400 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 4,
"total_runs": 400
}
},
"cumulative_failed_runs": 4,
"cumulative_total_runs": 400,
"first_seen": "2026-08-15",
"last_seen": "2026-09-09",
"nightly_count": 4,
"target": "//score/mw/com/test/methods/mixed_criticality/integration_test:asilb_consumer_asilb_provider_test"
}
```

Start with the Bazel target //score/mw/com/test/methods/mixed_criticality/integration_test:asilb_consumer_asilb_provider_test and run it under the gcc15-integration configuration. Inspect the test and its failure output to identify why it is intermittent. Done means the cause is addressed and repeated nightly or local runs no longer reproduce the flaky failures.

Written by the indexing model from the issue text.