eclipse-score / eclipse-score/communication

Flaky test: //score/mw/com/test/service_discovery_during_consumer_crash/integration_test:service_discovery_during_consumer_crash

Open
#875 5 comments 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/service_discovery_during_consumer_crash/integration_test:service_discovery_during_consumer_crash`

**Cumulative failed runs observed:** 6 (over 500 total runs, 5 nightlies)
**First seen:** 2026-08-08 · **Last seen:** 2026-09-14

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 6 | 500 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 6,
"total_runs": 500
}
},
"cumulative_failed_runs": 6,
"cumulative_total_runs": 500,
"first_seen": "2026-08-08",
"last_seen": "2026-09-14",
"nightly_count": 5,
"target": "//score/mw/com/test/service_discovery_during_consumer_crash/integration_test:service_discovery_during_consumer_crash"
}
```

Contributor guide

Open the contributing guide

Research direction

Start with the Bazel target //score/mw/com/test/service_discovery_during_consumer_crash/integration_test:service_discovery_during_consumer_crash and run it under the gcc15-integration configuration. Investigate the intermittent failures across the service-discovery and consumer-crash scenario; done means the target runs reliably without the observed flaky failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.