eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/concurrent_skeleton_creation/integration_test:concurrent_skeleton_creation
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/concurrent_skeleton_creation/integration_test:concurrent_skeleton_creation`
**Cumulative failed runs observed:** 4 (over 200 total runs, 2 nightlies)
**First seen:** 2026-08-05 · **Last seen:** 2026-08-08
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| qnx-integration | 4 | 200 |
```json
{
"configs": {
"qnx-integration": {
"failed_runs": 4,
"total_runs": 200
}
},
"cumulative_failed_runs": 4,
"cumulative_total_runs": 200,
"first_seen": "2026-08-05",
"last_seen": "2026-08-08",
"nightly_count": 2,
"target": "//score/mw/com/test/concurrent_skeleton_creation/integration_test:concurrent_skeleton_creation"
}
```
Contributor guide
Research direction
Start by locating the Bazel target //score/mw/com/test/concurrent_skeleton_creation/integration_test:concurrent_skeleton_creation and running it in the qnx-integration configuration. Inspect the test and its failure output to identify why it is intermittent. Done means the target no longer flakes across repeated runs or the issue records a reproducible cause and follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100