Automation Artifacts Layout

Automation Artifacts Layout

Fission stores generated benchmark and automation outputs under benchmark/artifacts/. Paths may grow over time—this page captures stable conventions you should rely on when reading CI uploads or local runs.

Top-level buckets

benchmark/artifacts/automation/      # nir-check / automation lane outputs
benchmark/artifacts/full_benchmark/ # Python full benchmark runner outputs

Treat anything outside these roots as experimental or legacy unless documented elsewhere.

Working copies vs CI

• Developers typically generate artifacts locally beside their checkout.
• CI jobs may zip or publish subsets—refer to upload-artifacts steps in .github/workflows/reusable-*.yml when chasing missing files.

Hygiene expectations

• Prefer .gitignore rules keeping large binaries out of commits unless explicitly curated fixtures under benchmark/binary/.
• When attaching artifacts to bug reports, prefer hashes + manifests (benchmark/config/) over multi-gigabyte dumps.

Related wiki pages

• Automated checks overview
• Full benchmark interpretation

Related repository docs

• benchmark/full_benchmark/README.md
• AGENTS.md (artifacts discipline)