eclipse-score / eclipse-score/communication
Flaky test: //quality/integration_testing/test:test_hello_world
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//quality/integration_testing/test:test_hello_world`
**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-08-23 · **Last seen:** 2026-08-23
### Per-config cumulative
| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 1 | 100 |
```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 1,
"cumulative_total_runs": 100,
"first_seen": "2026-08-23",
"last_seen": "2026-08-23",
"nightly_count": 1,
"target": "//quality/integration_testing/test:test_hello_world"
}
```
Contributor guide
Research direction
Start by running the target //quality/integration_testing/test:test_hello_world under the gcc15-integration configuration and capture the failure output. Inspect the target's test sources and setup to identify why the single observed failure is nondeterministic. Done means the cause is addressed and repeated runs no longer reproduce 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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100