eclipse-score / eclipse-score/communication

Flaky test: //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_assign_not_offered_skeleton_same_process_test

Open
#842 1 comment 0 reactions 0 assignees View on GitHub
flaky-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_assign_not_offered_skeleton_same_process_test`

**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-08-05 · **Last seen:** 2026-08-05

### 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-05",
"last_seen": "2026-08-05",
"nightly_count": 1,
"target": "//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_assign_not_offered_skeleton_same_process_test"
}
```

Contributor guide

Open the contributing guide

Research direction

Start with the Bazel target //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_assign_not_offered_skeleton_same_process_test and inspect its qnx-integration failure logs. Reproduce the test repeatedly in that configuration, identify the source of the intermittent failure, and verify that repeated runs no longer fail.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.