Skip to content

crons: the queue health report -- hourly one-screen truth (Closes #12613) - #12694

Merged
gHashTag merged 3 commits into
masterfrom
perf/queue-health-report-v2
Oct 26, 2026
Merged

gHashTag merged 3 commits into
masterfrom
perf/queue-health-report-v2

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Rebase of #12615 onto today's master (that branch sat DIRTY on the foreign-exceptions union while the queue moved under it; master-side merges are hook-blocked locally, so the branch is rebuilt server-side). Same content: the hourly workflow, its cron card, the exceptions entry with the owner's 2026-10-26 chat approval quoted. Supersedes #12615.

@gHashTag gHashTag added the owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR label Oct 26, 2026
@gHashTag
gHashTag enabled auto-merge (squash) October 26, 2026 16:28
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 16:28:59 UTC

Summary

Status Count
Total Open PRs 13
PRs with Failing Checks 13
PRs with All Checks Green 0
READY 0
FAILING 13
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag force-pushed the perf/queue-health-report-v2 branch from 216010d to 28d9104 Compare October 26, 2026 16:35
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 16:35:38 UTC

Summary

Status Count
Total Open PRs 13
PRs with Failing Checks 12
PRs with All Checks Green 1
READY 0
FAILING 12
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 12 + 0 + 0 = 12, and there are 13 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 17:04:03 UTC

Summary

Status Count
Total Open PRs 14
PRs with Failing Checks 14
PRs with All Checks Green 0
READY 0
FAILING 14
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@tri-claw

tri-claw Bot commented Oct 26, 2026

Copy link
Copy Markdown

Summary by t27-bees

Checked by the t27 compiler

t27c parse, parse-complete and typecheck on each changed .t27 file at 097c5e9. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/crons/trinity-queue-health-report.t27: parses and typechecks.

Read by the model

This PR adds an hourly GitHub Actions workflow that writes a read-only queue health report (counts by merge state, armed auto-merges, drafts, opt-outs) into a single GitHub issue, plus its cron spec and a foreign-exceptions entry with owner approval.

Worth a look

  • .github/workflows/queue-health-report.yml:12 – gh pr list --limit 200 caps results at 200 PRs; if the open queue exceeds that, counts will be incomplete and the report will silently under-report.
  • .github/workflows/queue-health-report.yml:14–20 – The jq filter only counts BLOCKED, DIRTY, CLEAN, UNSTABLE. GitHub also returns BEHIND, HAS_HOOKS, UNKNOWN, etc.; those PRs fall into no bucket and are omitted from the totals.
  • .github/workflows/queue-health-report.yml:22–24 – gh issue list --search "queue health report in:title" picks the first match (.[0]). If a second issue with that substring exists (e.g., a duplicate or a related issue), the workflow will overwrite the wrong one.
  • .github/workflows/queue-health-report.yml:6 – The cron 7 * * * * runs at minute 7 every hour; no timezone is declared in the workflow (the spec says UTC), but GitHub Actions cron defaults to UTC, so this is consistent.
  • tools/policy/foreign-exceptions.txt:538–542 – The exception entry references owner approval from 2026-10-26; the file path matches the added workflow.

Read: 3 files, +135 -0, the whole diff. Head 097c5e9. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 17:31:38 UTC

Summary

Status Count
Total Open PRs 13
PRs with Failing Checks 12
PRs with All Checks Green 1
READY 0
FAILING 12
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 12 + 0 + 0 = 12, and there are 13 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 172e309 into master Oct 26, 2026
25 of 36 checks passed
gHashTag added a commit that referenced this pull request Oct 26, 2026
…dates port (Closes #12710, Refs #12613 #12694) (#12713)

The yml for the card already on master (#12694), with its on: block fixed
(the original had a bare - cron: list -- the hourly schedule never
fired), plus the port of scripts/compare_gamma_candidates.py (broken
one-shot printer, SyntaxError at line 59, unreferenced) to
specs/port/scripts/compare_gamma_candidates.t27 -- 4/4 tests, sealed.
The deletion pays the yml's foreign lines: net -25.
dmitrii-f-t27 pushed a commit to dmitrii-f-t27/t27 that referenced this pull request Oct 30, 2026
…ity-S-AI-DNA#12727)

Which numbers moved and why, per the gate's own instruction:
- shell.txt: workflow files 69->71 (pr-queue-drain.yml landed via
  Trinity-S-AI-DNA#12694 and queue-health-report.yml via Trinity-S-AI-DNA#12713, neither carried a
  re-bless), jobs 99->101 and run: steps 340->342 (the two new files'
  jobs and steps).
- quiet.txt: files read 49->50 and named-a-path 273->276 (same two
  files), workflow files 69->71 as above.
- fetches.txt: re-recorded by `tri census pin --bless` for the same
  tree.
`tri census pin --gate` exits 0 on this tree. The guard/autofix/
rebase ymls of Trinity-S-AI-DNA#12710 will move the count again (72, 73) and each
carries its own bless in the same commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

owner-approved-foreign Owner-approved exception to the only-t27 rule: hand-written foreign code allowed in this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant