Print raw trial samples from the CSPA performance gate
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- c
- Domain
- performance, testing-qa
Research direction
Start in tests/test_cspa_perf_gate.c and compare its timed loop and output with tests/test_crdt_perf_gate.c. Emit the nine recorded trial values after measurement in sample order using a stable, parseable format, then add focused validation that confirms ordering and placement while preserving the existing summaries, sentinels, skip behavior, and exit status.
Written by the indexing model from the issue text.
Description
Discovery context
While diagnosing the required CRDT and CSPA performance regressions for #1913, review found that tests/test_cspa_perf_gate.c records nine ordered trial times but prints only summary statistics. The analogous tests/test_crdt_perf_gate.c prints every raw sample. Existing CSPA CI logs therefore cannot show whether a median/variance shift comes from an outlier or a consistent change.
Architect and Critic reviewed this gap and agreed it is useful general gate observability, but not required to complete #1913: paired invocation medians plus the current gate summaries and correctness/iteration sentinels suffice for that diagnosis.
Scope
Print all nine existing CSPA trial values after the timed loop in a stable, parseable order and format. Keep the diagnostic outside the measured interval and retain the current summaries and gate behavior.
Acceptance criteria
- All nine trial values are emitted in sample order on both passing and stable target-failure runs.
- The output format is stable and parseable.
- Correctness and iteration sentinels, target, CoV skip behavior, exit status, and mean/stdev/median calculations remain unchanged.
- A focused test or source-level validation confirms the values are emitted after measurement and in order.
Related: #1913, #1369.
- Dominant language
- C
- Stars
- 18
- Forks
- 2
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 148
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from semantic-reasoning/wirelog
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
semantic-reasoning/wirelog#2229 ·
Maintainers usually reply within 1 day
-
Doc: insert executor and incremental consolidation leave sorted runs, not globally sorted headsOpen
Difficulty 1/5 Under an hour Newbie friendliness 83/100
semantic-reasoning/wirelog#2133 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
semantic-reasoning/wirelog#2042 ·
Maintainers usually reply within 1 day
-
Recursive stratum at W>=2: refused final normalization leaves stale rows after a later removePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 54/100
semantic-reasoning/wirelog#2336 ·
Maintainers usually reply within 1 day
-
Step-completion cursor at W>=2 keeps input refused after any repeated post-merge failurePossibly taken @justinjoy claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 22/100
semantic-reasoning/wirelog#2329 · 1 comment ·
Maintainers usually reply within 1 day
All issues in semantic-reasoning/wirelog
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jniebuhr/gaggimate#1009 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sonic-net/sonic-buildimage#30563 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
llvm/offload-test-suite#1698 ·
Maintainers usually reply within 1 day
-
bug genc
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day