Skip to content

[WIP] Regular PR checking - #100

Open
ambergorzynski wants to merge 26 commits into
mainfrom
regular-pr-checking
Open

[WIP] Regular PR checking#100
ambergorzynski wants to merge 26 commits into
mainfrom
regular-pr-checking

Conversation

@ambergorzynski

Copy link
Copy Markdown
Collaborator

Adds periodic coverage-gap checking for open AMDGPU and SPIR-V PRs on llvm/llvm-project.

The new workflow discovers matching PRs via gh, re-runs fuzz-fill’s Docker-based Workflow 2 when a PR head SHA changes, records results in local state, and writes human-readable reports flagging PRs whose added lines aren’t covered by the regression suite.

Not ready for review yet - still sense-checking the analysis

Not added yet: scheduling for regular job

Introduces discover/plan/record subcommands with a versioned state.json
schema to track which AMDGPU and SPIR-V PRs need coverage-gap reruns.
Wraps build-image-pr.sh and pr-cov-gaps-detection.sh with discover/plan
execution, backend-specific Docker tags, and evaluate-output recording.
Introduces a report subcommand that writes latest.json and latest.md
from state using pandas for gap CSV loading and aggregation, and
wires report generation into check-llvm-prs after each run.
Adds config.example.env, scripts/pr-check/README.md with cron/systemd
examples, and a README cross-link for the check-llvm-prs workflow.
Covers pr_check state/plan/report helpers with mocked discovery, and
ignores local scripts/pr-check/config.env.
Move the flag onto discover, plan, and report so check-llvm-prs.sh can
pass it after the subcommand name without argparse errors.
This is required by current upstream LLVM CMake
Filter discovery with GitHub created:> instead of updated:>, so cron runs
target fresh PRs rather than stale branches that were only touched recently.
Use gh api search/issues for the date qualifier and expose --max-age-days /
PR_CHECK_MAX_AGE_DAYS (default 30).
Add guard to run report writing even if pr check fails while processing the pr queue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant