Flaky test: //score/mw/com/test/methods/semi_dynamic_methods/integration_test:semi_dynamic_methods_different_processes_test

## Flaky test: `//score/mw/com/test/methods/semi_dynamic_methods/integration_test:semi_dynamic_methods_different_processes_test`

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

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 2 | 200 |
| qnx-integration | 1 | 100 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 2,
"total_runs": 200
},
"qnx-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 3,
"cumulative_total_runs": 300,
"first_seen": "2026-08-08",
"last_seen": "2026-08-13",
"nightly_count": 3,
"target": "//score/mw/com/test/methods/semi_dynamic_methods/integration_test:semi_dynamic_methods_different_processes_test"
}
```

Start with the target //score/mw/com/test/methods/semi_dynamic_methods/integration_test:semi_dynamic_methods_different_processes_test and reproduce it in the gcc15-integration and qnx-integration configurations. Compare the failures across the three reported nightlies and identify the cause of the intermittent result. Done means the test passes reliably in both configurations and the flaky failures no longer recur.

Written by the indexing model from the issue text.