2.0.2 kit 1 (final) pair gate: node 94e4c6ba six node cells GREEN on build-4, pow and app GREEN on 77b5acc5; the rule-33 mac canary FAIL on its sync line (kit 1 the fallback, kit 2 the roll); batch 202-94e4c6ba-870c0344; F0's pair and canary rows
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs
parent
3fc04d9383
commit
aef1969d2f
3 changed files with 428 additions and 365 deletions
|
|
@ -53,8 +53,8 @@ The fixture every case of the Test and Acceptance Standard (docs/plans/igneum-2.
|
|||
| Same-work on the candidate (R2-F03-R02, R03) | on one job context (same-work-20261008-02, sha256 21d78fd4…, boundary nonce 1572864, day 20730 to 20731): the node reader PASS on all three phases (IgneumEngine::epoch_for_bounded, install_pow_genesis as the live miner calls it), the pool's D1-pairing reader PASS on all three phases (the share verifier's path), the CPU reference cross-checked twice against the hash lane's independent export (hl-v6-all-cs.tgz a4742bfe…, hl-v6-all-cs.txt b77c61d8…), CUDA on the 5090 and the 4090 phases 1 and 2 PASS with phase 3 and the 3090 running, every nonce bit for bit; OpenCL and Metal at 08:30 UK; the rows read NOT RUN in progress until the sixth reader (the spec's acceptance says every reader). Three reader faults recorded as faults, not disagreements (the engine-install class: a standalone engine process must call install_pow_genesis before the first epoch_for). | master b464021f and e95d32c9 (23:00 and 23:10 UK); build-1:/srv/artefacts/tas/same-work-20261008-02/ | same-work hand |
|
||||
| The acceptance rule on the candidate (6.13) | PASS under both era inputs in circulation; the edc4fa84 program (the candidate) clean at widths 4 and 1 under the full rule and the crate's own predicate; attack-f8 subset PASS | master 17dee5bc (lane D, 22:40 UK); batch family-gate-20261008c | lane D |
|
||||
| The live class v5 object (context 03) | 81fbfa3aa413173f at epoch 2 (epoch seed 3c3fab43…, day 20734), the live node's own program-id line as the witness; the same-work test's live-chain half, references about 00:25 UK, CUDA after them; labelled on an island, not a network | the hand's context 03 (build-1, sha256 53837a96…) | same-work hand |
|
||||
| 2.0.2 pair gate | Kit 1's node is release-2.0.2-node d657e490 (the fold minus fix 2) and the cut tip release-2.0.2 6b17f951 (the pin and the manifest's node block at d657e490, release-manifest-check green; no crate move since 77b5acc5): the node stream on d657e490 (the kaspad check with igneum-pow and the five node suites on the key-succession pairing with the class v5 freeze) runs on build-4 from 23:14 UK, its batch 202-d657e490-6b17f951 when it closes. The earlier sha a284380b (the fold with fix 2) read every node cell GREEN on build-4 (core 185/0, exec 93/0, miner 33/0, p2p-flows 39/0, consensus 143/0, the kaspad check green) and its pair read RED on the real chain at 23:12 UK (a fix-2 lock fault: the EVM RPC hung seven minutes during IBD and the proof asks timed out), so it is not the kit; its batch 202-a284380b-5f50afd1 (master 26203e35) stands as the record. The miner tip: pow 113/0, app 389/0 on 77b5acc5. Kit 2 (the fold re-cut with the fix-2 fix) gets its own batch when named. | the shipper's 23:1x line; build-1:/srv/artefacts/tas/202-a284380b-5f50afd1/ | CI steward, shipper, node lane |
|
||||
| Rule 33 canary for 2.0.2 | BLOCKED: no record yet; tools/ci/canary/5f50afd1.json with four blocks (fleet, hive, windows, mac) lands with the entries, each entry published on its own PASS block (publish-manifest.sh --release-sha) | the shipper's 22:3x line | shipper, fleet lane, relay lane |
|
||||
| 2.0.2 pair gate | Kit 1 (final): node release-2.0.2-node 94e4c6ba (d657e490 + the IBD body anchor on the heaviest validated header; without it every fresh node held at 4,379) and the cut tip release-2.0.2 870c0344 (the pin and the manifest's node block at 94e4c6ba, release-manifest-check green; no crate move since 77b5acc5): on build-4 from the key-succession parent with the class v5 freeze (fingerprint cbc5bd0a) the kaspad check with igneum-pow GREEN (rule 19), core 185/0, exec 92/0, miner 33/0, p2p-flows 40/0, consensus 143/0; the miner tip pow 113/0, app 389/0 on 77b5acc5. Batch 202-94e4c6ba-870c0344. The earlier shas stand as records: d657e490 (every cell GREEN, the 4,379 stall; batch 202-d657e490-6b17f951, master 76041234) and a284380b (every cell GREEN, the pair RED on chain at 23:12 UK, a fix-2 lock fault; batch 202-a284380b-5f50afd1, master 26203e35). Kit 2 (the fold re-cut with the fix-2 fix) gets its own batch when the HEAL lane names it. | the shipper's 23:4x line; build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/ | CI steward, shipper, node lane |
|
||||
| Rule 33 canary for 2.0.2 | Kit 1 (870c0344, node 94e4c6ba): the mac block FAIL on its sync line (the fresh node on the project's macOS machine wedged at DAA 9,821: the executor behind the exec state lock, the exec RPC answering nothing; build-1:/srv/canary/870c0344/mini/00-verdict.txt, 04-sync.txt), so no 2.0.2 entry publishes on kit 1 and publish-manifest's guard holds; the fleet does not roll kit 1 (the class is nondeterministic); kit 1's artefacts are the fallback. The roll and the entries come on kit 2 (fix 2, the record store, the HEAL lane's wedge fix; named by 01:00 UK) once its four-block record reads PASS; F0's 2.0.2 row names kit 2 then. | the shipper's 00:0x line; the coordinator's ruling | shipper, fleet lane, relay lane, HEAL lane |
|
||||
| Network label | devnet-4 has been islands since the epoch-3 cut: every measurement recorded on the 2.0 devnet after 20:00 UK reads "on an island, not a network" until the fleet is one chain (the 2.0.2 roll as the convergence test, else the operator reset onto hub-1's chain at 04:00) | main's word through the coordinator, 22:2x UK; the recorder's --label-islands | CI steward |
|
||||
|
||||
The block is the steward's read-back of the lanes' own landed lines; the three roles in the signatures table sign by a landing of their own.
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
80
tools/ci/batches/202-94e4c6ba-870c0344.json
Normal file
80
tools/ci/batches/202-94e4c6ba-870c0344.json
Normal file
|
|
@ -0,0 +1,80 @@
|
|||
{
|
||||
"run_id": "202-94e4c6ba-870c0344",
|
||||
"manifest_sha": "94e4c6ba",
|
||||
"cut_tip": "870c0344 (miner; pow and app cells on 77b5acc5, no crate move since); node 94e4c6ba on the key-succession pairing with the class v5 freeze (fingerprint cbc5bd0a)",
|
||||
"evidence_dir": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344",
|
||||
"boxes": [
|
||||
"build-4"
|
||||
],
|
||||
"method": "native",
|
||||
"note": "2.0.2 pair gate on build-4, 22:52 UTC: kit 1 (final): release-manifest-check green on 870c0344 (node block kit1-line 94e4c6ba); 77b5acc5..870c0344 moves pool/ and packaging only; 94e4c6ba = d657e490 + the IBD body anchor on the heaviest validated header (without it every fresh node held at 4,379); d657e490's batch 202-d657e490-6b17f951 (master 76041234) and a284380b's (26203e35) stand as the records of those shas Every suite cell maps its cases partially, so the green suites read NOT RUN in progress with their logs as evidence, never PASS by inference. Kit 1's rule-33 canary: the mac block FAIL (the sync line), recorded on INT-07; kit 1 is the fallback, not the roll.",
|
||||
"cells": [
|
||||
{
|
||||
"cell": "suite:pow",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/miner-77b5acc5/box4-pow.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; pow on release-2.0.2 77b5acc5 (box4, 226s); 77b5acc5..870c0344 moves no crate, so the cell covers the tip by content",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:app",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/miner-77b5acc5/box4-app.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; app on release-2.0.2 77b5acc5 (box4, 39s); 77b5acc5..870c0344 moves no crate, so the cell covers the tip by content",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "check:freeze",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-kaspad-check.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; kaspad-check on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 26s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:core",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-core.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; core on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 25s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:exec",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-exec.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; exec on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 45s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:miner",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-miner.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; miner on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 45s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:p2p-flows",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-p2p-flows.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; p2p-flows on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 45s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "suite:consensus",
|
||||
"status": "NOT RUN",
|
||||
"evidence": "build-1:/srv/artefacts/tas/202-94e4c6ba-870c0344/node-94e4c6ba/box4-consensus.log",
|
||||
"note": "suite GREEN (rc 0, every test passed); the cell covers its cases partially, so the case reads NOT RUN in progress with this evidence until its own acceptance is exercised; consensus on release-2.0.2-node 94e4c6ba with the key-succession parent and the class v5 freeze igneum-pow (box4, 44s)",
|
||||
"in_progress": true
|
||||
},
|
||||
{
|
||||
"cell": "canary:fresh-install",
|
||||
"cases": [
|
||||
"INT-07"
|
||||
],
|
||||
"status": "FAIL",
|
||||
"method": "team-reported",
|
||||
"evidence": "build-1:/srv/canary/870c0344/mini/00-verdict.txt; build-1:/srv/canary/870c0344/mini/04-sync.txt",
|
||||
"network_label": "on an island, not a network",
|
||||
"note": "rule 33 on kit 1 (tip 870c0344, node 94e4c6ba): the mac block reads FAIL on its sync line; the fresh node on the project's macOS machine wedged at DAA 9,821 (the executor behind the exec state lock, the exec RPC answering nothing), so no 2.0.2 entry publishes on kit 1 (publish-manifest's guard holds) and the fleet does not roll it (the coordinator's ruling: the class is nondeterministic); kit 1's artefacts stay the fallback; the roll and the entries come on kit 2 (fix 2, the record store, the HEAL lane's wedge fix; named by 01:00 UK). The shipper's line 00:0x UK."
|
||||
}
|
||||
]
|
||||
}
|
||||
Loading…
Reference in a new issue