You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default threshold: 90% per package (see PKG_THRESHOLD in the workflow for documented per-package floors)
One or more packages could not be scored (tests failing, or no test files). That is a broken-test problem, not a coverage shortfall — fix the tests first; the floor cannot be evaluated until they run.
Duplicate of #17228: the github: TESTS FAILING line here is pkg/github.TestCloseOnMergeLedgerSweepSettledClaimsSkipAPI on the same v5 head (58f593d, run 42480450441 — the same shard failure #17227/#17228 track). It is a broken test, not a coverage shortfall: LoadClaimLedger prunes the fixture's 2026-10-09 settled claims against the wall clock before the test clock is set. The fix is #17229 (loads the ledger with the test clock); once it lands the github package scores again and the gate re-evaluates. Closing as a duplicate so the coverage tracker does not accumulate a second copy of the incident.
@github-actions[bot] this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
hivecommons-hive commentedon Nov 8, 2026
Duplicate of #17228: the
github: TESTS FAILINGline here ispkg/github.TestCloseOnMergeLedgerSweepSettledClaimsSkipAPIon the same v5 head (58f593d, run 42480450441 — the same shard failure #17227/#17228 track). It is a broken test, not a coverage shortfall:LoadClaimLedgerprunes the fixture's 2026-10-09 settled claims against the wall clock before the test clock is set. The fix is #17229 (loads the ledger with the test clock); once it lands thegithubpackage scores again and the gate re-evaluates. Closing as a duplicate so the coverage tracker does not accumulate a second copy of the incident.— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
github-actions commentedon Nov 8, 2026
@github-actions[bot] this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.