Vivarium
  • English

      • Branch-fix comparison

      // REPRO COMPARE · v1

      branch-fix vs original.

      Drop a verdict bundle from branch-fix-verdict.yml and see your fix line up against the deployed snapshot. All parsing happens locally — your verdicts never leave this browser.

      // THREE WAYS TO LOAD A VERDICT

      Bring a verdict bundle, three ways.

      Every comparison starts with a Contract v1 verdict from your branch fix. Use whichever path fits how the bundle reached you.

      DROP

      Drop the bundle

      Drag a branch-fix-verdict.yml artefact (zip) — or a bare verdict.json — onto the page. Original is auto-fetched from the deployed snapshot.

      PASTE

      Paste verdict JSON

      Paste the branch-fix and (optionally) original verdict.json payloads directly. Useful when CI logs are the only handle you have.

      SLUG + URL

      Type the slug

      Enter a recipe slug (e.g. pandas/56679) — the deployed snapshot loads automatically; supply your branch-fix verdict URL or drop file alongside.

      // 01 · LOAD VERDICTS

      Drop a verdict bundle here

      `.zip` from a workflow run, or a single `branch-fix-verdict.json` / `original-verdict.json`.

      or pick a fileAccepted: `.zip`, `.json`

      // 02 · PASTE FALLBACK

      // HOW TO PRODUCE A BUNDLE

      1. Build and publish your branch-fix Docker image to a registry the GitHub Actions runner can pull from.
      2. Run `gh workflow run branch-fix-verdict.yml -f slug=<slug> -f branch_image=<ref>`. The workflow lives at `.github/workflows/branch-fix-verdict.yml`.
      3. Download the artefact named `branch-fix-verdict-<slug>-<run_id>` from the run page.
      4. Drop the zip onto this page. Original is fetched from the deployed snapshot automatically.

      Pipeline spec → /vivarium/spec/branch-fix-pipeline

      // VERDICT SEMANTICS

      `reproduced` means the upstream bug was reproduced; `unreproduced` means it was not. A working branch-fix flips the verdict from `reproduced` to `unreproduced`.