eclipse-score / eclipse-score/communication

Flaky test: //score/mw/com/test/methods/non_trivial_constructors/integration_test:non_trivial_constructors_test

Open
#871 2 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/methods/non_trivial_constructors/integration_test:non_trivial_constructors_test`

**Cumulative failed runs observed:** 2 (over 200 total runs, 2 nightlies)
**First seen:** 2026-08-07 · **Last seen:** 2026-08-08

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| qnx-integration | 2 | 200 |

```json
{
"configs": {
"qnx-integration": {
"failed_runs": 2,
"total_runs": 200
}
},
"cumulative_failed_runs": 2,
"cumulative_total_runs": 200,
"first_seen": "2026-08-07",
"last_seen": "2026-08-08",
"nightly_count": 2,
"target": "//score/mw/com/test/methods/non_trivial_constructors/integration_test:non_trivial_constructors_test"
}
```

Contributor guide

Open the contributing guide

Research direction

Start by running //score/mw/com/test/methods/non_trivial_constructors/integration_test:non_trivial_constructors_test in the qnx-integration configuration and inspect its failure output. Compare the two failed runs with successful runs to identify the intermittent condition; done means the target no longer fails intermittently in the reported configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.