Skip to content

t27os: run vf_diff_main via CI Zig path and save diff artifact (M0 evidence, Refs #14021) #14024

Closed

Description

@gHashTag

The native Mach-O build of vf_diff_main.t27 exits 133 (trap stub) on the Mac, blocking all M0 pixel-diff evidence for epic #13426. The spec must be exercised through the generated Zig path in CI where a writable data section exists, until #14021 fixes the Mach-O code generator.

Boundary

  • specs/t27os/vf_diff_main.t27
  • .github/workflows/vf-diff-ci.yml

User Scenarios

  • Given specs/t27os/vf_diff_main.t27 and two P6 frames as CI artifacts, when the CI job runs the Zig-generated binary, then it prints a pixel-diff count and exits 0, and the count is uploaded as an artifact.
  • Given the same frame as both inputs, when the diff binary runs, then it prints a zero diff count (negative control).

Requirements

  • FR-001: A CI job MUST build vf_diff_main.t27 via the generated Zig path and run it on two stored P6 frames, producing a diff count artifact.
  • FR-002: The job MUST run a same-file negative control (zero diff) and a cross-frame positive control (non-zero diff).
  • FR-003: The artifact MUST include the sha256 of both input frames and the diff count.

Success Criteria

  • CI job exits 0 with a named artifact containing diff count and frame sha256s.
  • Same-file control prints 0 diffs, 0 runs exit with a non-zero diff on that control.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions