NIR Check In CI

NIR-check and CI

Continuous integration runs nir-check as part of heavy validation on main (scheduled nightly runs and pushes), separate from the lighter PR fast gate.

Where it lives in workflows

The reusable workflow .github/workflows/reusable-nir-check.yml is invoked from .github/workflows/ci-heavy.yml with inputs such as profile (run_profile), limits (functions_limit), and artifact publication toggles.

Inspect those files on main for exact arguments—they evolve with automation needs.

Why CI runs it

nir-check validates structuring / normalization regressions against curated manifests and emits artifacts suitable for reviewer inspection. Keeping this lane green protects deterministic comparisons used by benchmarks.

Local reproduction

Always reproduce failures locally before chasing infra flakes:

cargo run -p fission-automation -- nir-check --lane nir

Consult crates/fission-automation/ docs for lane semantics and statistics contracts aligned with NirBuildStats (see AGENTS.md pointers).

Related wiki pages

• Automated checks overview
• Automation artifacts layout
• CI/CD overview for contributors

Related repository docs

• .github/workflows/ci-heavy.yml
• .github/workflows/reusable-nir-check.yml
• .github/CI_CD_GUIDE.md