Flaky test: //score/mw/com/impl/bindings/lola:transaction_log_rollback_executor_test

## Flaky test: `//score/mw/com/impl/bindings/lola:transaction_log_rollback_executor_test`

**Cumulative failed runs observed:** 14 (over 3600 total runs, 11 nightlies)
**First seen:** 2026-08-08 · **Last seen:** 2026-09-14

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| asan-ubsan-lsan | 5 | 1200 |
| gcc15-unit | 7 | 1800 |
| gcc15-unit-shard1 | 1 | 300 |
| tsan | 1 | 300 |

```json
{
"configs": {
"asan-ubsan-lsan": {
"failed_runs": 5,
"total_runs": 1200
},
"gcc15-unit": {
"failed_runs": 7,
"total_runs": 1800
},
"gcc15-unit-shard1": {
"failed_runs": 1,
"total_runs": 300
},
"tsan": {
"failed_runs": 1,
"total_runs": 300
}
},
"cumulative_failed_runs": 14,
"cumulative_total_runs": 3600,
"first_seen": "2026-08-08",
"last_seen": "2026-09-14",
"nightly_count": 11,
"target": "//score/mw/com/impl/bindings/lola:transaction_log_rollback_executor_test"
}
```

Start by running the `//score/mw/com/impl/bindings/lola:transaction_log_rollback_executor_test` target repeatedly in the listed configurations and capture the failing output. Inspect the test and the transaction-log rollback executor paths revealed by the failures; done means the test no longer flakes across the affected configurations.

Written by the indexing model from the issue text.