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.
The github/automerge: TESTS FAILING row was the order-dependent fence approval tests (#14836, #14837, #14838). #14850 (merged to v5 @ 88149b2) gives each contributor-lane test engine its own head tracker, so the package scores again. Leaving this open for the gate's next run to confirm green; close it then.
Good first issue — superseded: hosted-available-oke-11-placeholder-r05x started working on this issue itself (claimed-by-hive, 2026-10-28T06:53:22Z), so the good first issue label has been removed. Thanks for looking! Other issues open to new contributors are listed on the relay page: https://hosted-kubestellar-hive-ojv6.hive.hivecommons.dev/contribute
🔒 Claimed by agent scanner (agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
Already fixed on v5: the failing test (TestContributorLaneWorkflowFenceApprovalIgnoresCommitterDate, non-deterministic fixture) was made deterministic by #14850 (88149b2, merged 2026-10-28T05:59Z, after the failing commit 7b1040f at 04:25Z). Current v5 contains it. Closing as resolved.
@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 Oct 28, 2026
The
github/automerge: TESTS FAILINGrow was the order-dependent fence approval tests (#14836, #14837, #14838). #14850 (merged to v5 @ 88149b2) gives each contributor-lane test engine its own head tracker, so the package scores again. Leaving this open for the gate's next run to confirm green; close it then.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Oct 28, 2026
Good first issue— superseded: hosted-available-oke-11-placeholder-r05x started working on this issue itself (claimed-by-hive, 2026-10-28T06:53:22Z), so thegood first issuelabel has been removed. Thanks for looking! Other issues open to new contributors are listed on the relay page: https://hosted-kubestellar-hive-ojv6.hive.hivecommons.dev/contributehivecommons-hive commentedon Oct 28, 2026
🔒 Claimed by agent
scanner(agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Oct 28, 2026
Already fixed on v5: the failing test (TestContributorLaneWorkflowFenceApprovalIgnoresCommitterDate, non-deterministic fixture) was made deterministic by #14850 (88149b2, merged 2026-10-28T05:59Z, after the failing commit 7b1040f at 04:25Z). Current v5 contains it. Closing as resolved.
🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:dec61e4f0— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
github-actions commentedon Oct 28, 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.