eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_different_process_test
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_different_process_test`
**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-08-11 · **Last seen:** 2026-08-11
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| qnx-integration | 1 | 100 |
```json
{
"configs": {
"qnx-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 1,
"cumulative_total_runs": 100,
"first_seen": "2026-08-11",
"last_seen": "2026-08-11",
"nightly_count": 1,
"target": "//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_different_process_test"
}
```
Contributor guide
Research direction
Start with the Bazel target //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_different_process_test and run it under the qnx-integration configuration. Investigate why the test failed once across 100 runs, then verify the failure no longer recurs in repeated runs or nightlies.
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