eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/generic_proxy/integration_test:generic_proxy
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/generic_proxy/integration_test:generic_proxy`
**Cumulative failed runs observed:** 2 (over 200 total runs, 2 nightlies)
**First seen:** 2026-08-10 · **Last seen:** 2026-08-18
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 1 | 100 |
| qnx-integration | 1 | 100 |
```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 1,
"total_runs": 100
},
"qnx-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 2,
"cumulative_total_runs": 200,
"first_seen": "2026-08-10",
"last_seen": "2026-08-18",
"nightly_count": 2,
"target": "//score/mw/com/test/generic_proxy/integration_test:generic_proxy"
}
```
Contributor guide
Research direction
Start by running the named target, //score/mw/com/test/generic_proxy/integration_test:generic_proxy, in the gcc15-integration and qnx-integration configurations. Inspect the failures and the target's integration-test setup to identify why the two nightly runs failed. Done means the target runs reliably in both reported configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100