From 36cf81535e061851b6ff0bcee687cfd19a7570e4 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 09:12:09 +0000 Subject: [PATCH] docs: 7.7.2 the feature-gated witness-order test is a deterministic red on the 0.3.19 tree, compiled by no suite line Co-Authored-By: Claude Fable 5.1 --- docs/plans/counter-asic-3-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plans/counter-asic-3-node.md b/docs/plans/counter-asic-3-node.md index 1d2e0688c..91ea33f98 100644 --- a/docs/plans/counter-asic-3-node.md +++ b/docs/plans/counter-asic-3-node.md @@ -344,7 +344,7 @@ Renumbered 09:3x UK: the feature tree is 0.3.19 (mirror branch release-0.3.19-no The merge surfaced a test-order race both parents carry: the class-signal and ladder tables are process-wide statics, two tests install and restore them (`block_template_uses_current_block_version`, `cheap_checks_run_before_the_pow_engine`), and any block-building test of the same binary inside that window reads `WrongBlockVersion(1026 or 32770, 2)`; 1 of 112 then 4 of 112 under a box load of 178, 2 of 112 on the quiet box, and the 0.3.17 suite's "two load flakes that pass alone" were the same reading. Fix in 1cf43254 (and on ca3-v4-0318): the two installing tests are their own test targets (`consensus/tests/igneum_installed_signals.rs`, `consensus/tests/igneum_order_tests.rs`), one process each, and `INSTALL_TEST_LOCK` orders installers that share a binary; `cargo test -p kaspa-consensus --lib` no longer covers them, the crate without `--lib` does. -Two environment facts for anyone building the release tree under this worktree: `kaspa-pow` links only against the igneum-pow at the ladder commit (0a1faa1c, branches ladder and release-0.3.18 of the igneum repo), which this worktree's parent predates (an untracked cargo `paths` override to a copy beside the fork does it); and `igneum-exec` includes the proving ELF manifest and keys from `proving/igneum-prove/elf/` five directories up, which the box mirror of the parent had to be given by hand. +A red nobody's suite line compiles: `processes::pruning_proof::igneum_m20_tests::witnesses_are_checked_in_epoch_order_under_their_own_seeds` sits behind `#[cfg(feature = "igneum-pow")]` and fails deterministically (MissingEpochSeed(1, _, 109) not matched) alone on an untouched e69e8a39 with the feature on (the testnet lane, 08:52 UK, box load under 10; the decimals lane saw it on eec34ac3), so every "111 passed" above excludes it by construction; the M20 pruning-proof witness work owns it. Two environment facts for anyone building the release tree under this worktree: `kaspa-pow` links only against the igneum-pow at the ladder commit (0a1faa1c, branches ladder and release-0.3.18 of the igneum repo), which this worktree's parent predates (an untracked cargo `paths` override to a copy beside the fork does it); and `igneum-exec` includes the proving ELF manifest and keys from `proving/igneum-prove/elf/` five directories up, which the box mirror of the parent had to be given by hand. ### 7.7.3 The exec RPC crash on an empty state (the join gate's second finding, 7 October 2026, c6a62e00)