Skip to content

ci(lock): check out pinned consensus + primitives next to spec-lock for the lock tests - #3

Open
secsovereign wants to merge 3 commits into
mainfrom
fix/ci-check-out-lock-sources
Open

secsovereign wants to merge 3 commits into
mainfrom
fix/ci-check-out-lock-sources

Conversation

@secsovereign

Copy link
Copy Markdown
Member

Main is red at 6382e2c (run 40022891446, zeus-workstation-2): 67 of 139 lib tests panic with ENOENT because production_lock reads ../blvm-consensus/src/... and ../blvm-primitives/src/..., and the Test job only checks out spec-lock. The earlier green at 3a55aeb ran on zeus-workstation, which already had a blvm-consensus dir next to the workspace, so it read whatever leftover sources were on disk.

This makes the Test job check out spec-lock into blvm-spec-lock/, with blvm-consensus pinned at 994480d (v0.1.70 main) and blvm-primitives pinned at 9720541 (0.1.30 main) beside it. Nothing skips: missing sources still fail the job.

Locally with that layout (rust 1.88.0, cargo test --workspace --all-features --no-fail-fast), the 67 lock failures are gone. One CI failure is left, and this PR doesn't fix it:

  • published_gate_matches_the_table (new in 6382e2c) also reads ../docs/FORMAL_VERIFICATION_PLAN.md and ../docs/README.md. I can't find that file in any BTCDecoded repo, so it needs that docs tree pushed somewhere CI can check out.

Box-only noise, not CI: u64_shl_wraps_when_the_top_bit_is_set returns Unknown on my machine (it passes in CI), and the extract_* integration tests failed only because I used a custom CARGO_TARGET_DIR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant