eclipse-score / eclipse-score/communication

Flaky test: //score/mw/com/test/partial_restart/provider_restart_max_subscribers/integration_test:provider_restart_max_subscribers_no_proxy

Open
#879 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/partial_restart/provider_restart_max_subscribers/integration_test:provider_restart_max_subscribers_no_proxy`

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

### 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-08",
"last_seen": "2026-08-08",
"nightly_count": 1,
"target": "//score/mw/com/test/partial_restart/provider_restart_max_subscribers/integration_test:provider_restart_max_subscribers_no_proxy"
}
```

Contributor guide

Open the contributing guide

Research direction

Start by running the named Bazel target, //score/mw/com/test/partial_restart/provider_restart_max_subscribers/integration_test:provider_restart_max_subscribers_no_proxy, under the qnx-integration configuration. Inspect the partial-restart provider-restart test and its failure output to identify the intermittent behavior; done means the target passes reliably across repeated runs.

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.