eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier
- 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`
**Cumulative failed runs observed:** 3 (over 300 total runs, 3 nightlies)
**First seen:** 2026-08-07 · **Last seen:** 2026-08-11
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| qnx-integration | 3 | 300 |
```json
{
"configs": {
"qnx-integration": {
"failed_runs": 3,
"total_runs": 300
}
},
"cumulative_failed_runs": 3,
"cumulative_total_runs": 300,
"first_seen": "2026-08-07",
"last_seen": "2026-08-11",
"nightly_count": 3,
"target": "//score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier"
}
```
Contributor guide
Research direction
Start by locating the Bazel target //score/mw/com/test/fields/set_and_notifier/integration_test:test_notifier and run it in the qnx-integration configuration. Review the test and its recent failures to identify the intermittent behavior. Done means the target passes reliably across repeated nightly runs without reproducing the flake.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100