eclipse-score / eclipse-score/communication
Flaky test: //score/mw/com/test/fields/field_initial_value/integration_test:test_field_initial_value
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
## Flaky test: `//score/mw/com/test/fields/field_initial_value/integration_test:test_field_initial_value`
**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-09-05 · **Last seen:** 2026-09-05
### 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-09-05",
"last_seen": "2026-09-05",
"nightly_count": 1,
"target": "//score/mw/com/test/fields/field_initial_value/integration_test:test_field_initial_value"
}
```
Contributor guide
Research direction
Start by running the named target, //score/mw/com/test/fields/field_initial_value/integration_test:test_field_initial_value, under the gcc15-integration configuration and capture its failure output. Trace the intermittent behavior from the test and its exercised code; done means the target passes consistently across repeated integration runs.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100