eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/methods/edge_cases_test/integration_test:skeleton_recreation_test
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/methods/edge_cases_test/integration_test:skeleton_recreation_test`
**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-09-14 · **Last seen:** 2026-09-14
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 1 | 100 |
```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 1,
"cumulative_total_runs": 100,
"first_seen": "2026-09-14",
"last_seen": "2026-09-14",
"nightly_count": 1,
"target": "//score/mw/com/test/methods/edge_cases_test/integration_test:skeleton_recreation_test"
}
```
Contributor guide
Research direction
Start with the named target //score/mw/com/test/methods/edge_cases_test/integration_test:skeleton_recreation_test and run it under the gcc15-integration configuration. Investigate why the test is intermittent and confirm the fix by repeating the target enough times to establish that the flake no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100