Skip to content

Fix usage report missing-data coverage and continuation priority - #146

Merged
woksin merged 2 commits into
mainfrom
fix/usage-report-missing-data-133
Oct 5, 2026
Merged

woksin merged 2 commits into
mainfrom
fix/usage-report-missing-data-133

Conversation

@woksin

@woksin woksin commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Fixed

  • Actions usage reports now distinguish unstarted run inventories from partial inventories and identify the creation-time cutoff before which runs may be missing when collection stops. Job continuation pages share newest-first priority with initial pages, keeping budget-limited collection focused on newer runs. (Usage report: precise missing-data messages under a budget cut #133)

@woksin woksin self-assigned this Oct 5, 2026
@woksin

woksin commented Oct 5, 2026

Copy link
Copy Markdown
Contributor Author

Local verification: python3 -B .github/scripts/tests/actions-usage-report.test.py passed all 37 tests through pi-phase (120-second execution limit, 30-second queue limit). This is the exact check run by Verify Actions Usage Report; this automation repository has no application build or integration lane for these files. git diff --check passed. No workflows changed, so actionlint was not applicable. The managed quality-gate configuration has no matching Python gates. Live usage collection and issue publication were not exercised.

The regression fixtures cover inventories with no completed window (including a partially fetched first window), the precise cursor after completed empty and populated windows, and newest-first continuation scheduling even when the older continuation is returned first, with only one continuation request left in the budget.

Issue item 3 is already covered: the body of #129 mentions the alert above 300 weighted private hosted minutes a week, so this PR does not change that release note.

Assigned to woksin; GitHub cannot request review from the PR's author (woksin). Do not merge as part of this task; the owner will decide when to merge. The isolated worktree remains at /Volumes/sourcecode/repos/cratis/.worktrees/workflows-133.

@woksin
woksin merged commit bd23bcc into main Oct 5, 2026
@woksin
woksin deleted the fix/usage-report-missing-data-133 branch October 5, 2026 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant