mirror of
https://github.com/bdbrown4/peltier.io.git
synced 2026-11-07 10:58:28 +00:00
Claude
f2e9036196
The kernel lane (PR #14) added a second binary to the diff-test crate (src/bin/fp-compare.rs), which made `cargo run -p diff-test -- <target>` — the exact invocation the target-gates-no-net CI job uses to run a target's equivalence gate — ambiguous: error: `cargo run` could not determine which binary to run. available binaries: diff-test, fp-compare Naming the primary binary via `default-run` restores the single-binary behavior without touching the CI workflow or the gate command. Regression was latent on main since #14 merged; this PR's CI re-run surfaced it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EcKPWQ3MQD4NdEHwar96u2
21 lines
718 B
TOML
21 lines
718 B
TOML
[package]
|
|
name = "diff-test"
|
|
description = "Layered equivalence gates: upstream tests, golden replay, differential fuzzing, sanitizers; hash-pinned corpora"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
repository.workspace = true
|
|
# The crate ships two binaries — the `diff-test` gate driver and the
|
|
# `fp-compare` kernel-lane helper (src/bin/fp-compare.rs). Name the primary
|
|
# one so `cargo run -p diff-test` stays unambiguous (CI runs it as the
|
|
# per-target gate: `cargo run -p diff-test -- <target>`).
|
|
default-run = "diff-test"
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
serde.workspace = true
|
|
clap.workspace = true
|
|
sha2.workspace = true
|
|
thiserror.workspace = true
|
|
toml.workspace = true
|