eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier_same_process
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier_same_process`
**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-08-10 · **Last seen:** 2026-08-10
### 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-10",
"last_seen": "2026-08-10",
"nightly_count": 1,
"target": "//score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier_same_process"
}
```
Contributor guide
Research direction
Start by running //score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier_same_process in the qnx-integration configuration and collect the failure output. Inspect the test and its surrounding set-and-notifier integration code to identify the intermittent condition; done means the target passes consistently across repeated runs and the flaky failure is addressed.
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
- 48/100