Flaky test: //score/mw/com/test/multiple_proxies/integration_test:multiple_proxies

## Flaky test: `//score/mw/com/test/multiple_proxies/integration_test:multiple_proxies`

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

### 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-12",
"last_seen": "2026-09-05",
"nightly_count": 4,
"target": "//score/mw/com/test/multiple_proxies/integration_test:multiple_proxies"
}
```

Start with the Bazel target //score/mw/com/test/multiple_proxies/integration_test:multiple_proxies under the gcc15-integration configuration and reproduce the intermittent failure. Inspect the failure output and surrounding test behavior to identify the cause. Done means the target passes reliably across repeated runs and no longer appears in flaky-test reports.

Written by the indexing model from the issue text.