Preflight summary counter miscounts (prints FAIL=1 with zero failing checks)

Open Beginner friendly
#475 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start in tools/preflight_us_release_gates.py and reproduce the reported human-readable summary using the cited v9.2 feed and populace main inputs. Trace how the displayed FAIL and AT-RISK counts are computed, compare them with the --json-out records, and confirm done when the summary reports zero FAIL, one AT-RISK, and three PASS checks while preserving the correct exit code and JSON.

Written by the indexing model from the issue text.

Description

tools/preflight_us_release_gates.py printed Overall: AT_RISK (exit 2) [FAIL=1, AT-RISK=2, clean=0] on a run whose own --json-out records exactly: selection_carryover PASS, zero_support_preview PASS, export_mass_parity_risk AT_RISK, smoke_probe_support PASS — no FAIL, one AT-RISK, three passes. Exit code and JSON are right; the human-readable tally is wrong. Cosmetic but it reads as a failing gate to an operator. Repro inputs: v9.2 feed 61b115c0…, populace main 4746aba.

Dominant language
Python
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
88

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PolicyEngine/microcosm

All issues in PolicyEngine/microcosm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.