From 6f95751e06ebdb40c404a653b6ba1cc6508b691f Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Mon, 5 Oct 2026 23:18:28 +0000 Subject: [PATCH] Windows payload inputs: node 89dfcb95 (push-inputs.sh, the PC 2 build, the class-aware workers, signed); release-0.3.11 plan: the PC 2 job Co-Authored-By: Claude Fable 5.1 --- docs/plans/release-0.3.11.md | 2 +- packaging/windows/node-source.pin | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/plans/release-0.3.11.md b/docs/plans/release-0.3.11.md index ac673664..ad54c5c7 100644 --- a/docs/plans/release-0.3.11.md +++ b/docs/plans/release-0.3.11.md @@ -74,7 +74,7 @@ no 9070 XT; the hardware events are being corrected). The relay machine should b and the PC 1 box get its own agent (section 11). The Mac cross-build fallback for the Windows exes was announced and not started: the combined PC 2 job replaced it within the minute. -| PC 2 combined job | `IGNEUM_WIN_RELEASE=/target-integration/x86_64-pc-windows-gnu/release node tools/build-job.mjs run --node vendor/igneum-node-0311 --target 1ccfe586 --targets linux,windows --node-tests "kaspa-consensus kaspa-consensus-core igneum-exec kaspa-pow igneum-miner kaspa-p2p-flows" --app-tests igneum-app` from this worktree (its own zip `build-inputs-20261005230716-50058.zip`); PC 1's job removed from the jobs file so nothing double-places the exes | job `build-20261005-230745`, published 23:07:45Z (PC 2 woken), the first job on PC 2's re-set schedule. (pending: the stages, the suites, the exes) | +| PC 2 combined job | `IGNEUM_WIN_RELEASE=/target-integration/x86_64-pc-windows-gnu/release node tools/build-job.mjs run --node vendor/igneum-node-0311 --target 1ccfe586 --targets linux,windows --node-tests "kaspa-consensus kaspa-consensus-core igneum-exec kaspa-pow igneum-miner kaspa-p2p-flows" --app-tests igneum-app` from this worktree (its own zip `build-inputs-20261005230716-50058.zip`); PC 1's job removed from the jobs file so nothing double-places the exes | job `build-20261005-230745`, published 23:07:45Z (PC 2 woken), the first job on PC 2's re-set schedule; started 23:09Z, done 23:16:49Z (469 s): the Linux stage, the Windows stage 264 s, the test stage `RESULT test node [kaspa-consensus kaspa-consensus-core igneum-exec kaspa-pow igneum-miner kaspa-p2p-flows] exit 0 54 s` and `RESULT test app/igneum-app [igneum-app] exit 0 6 s`; 9 outputs verified and placed: igneumd.exe be8e83c07aeae5eb6842768071735289f3ef149ed9a7088592d8c54a4c252c08 (51,321,856), igneum-miner.exe 1ba1a249e2a21d52087a81f61f37cd2e1e3273c7ec8809ef9cfaa98f015895ce (10,987,520), igneum-app.exe ab104cc0... (3,065,344, the PC's; the installer's engine is the runner's), Linux igneumd d7a2715e... (49,193,960, glibc 2.39, HiveOS), igneum-miner 09d05ff6..., igneum-app 222f30c0... | | PC 2 suites | waits for the Counter ASIC coordinator's "PC 2 suites go" (agg-cost-pc2-3 on PC 2 until about 22:59Z) | (pending) | ### 3a. PC 1's app down (22:31 to 22:5xZ) diff --git a/packaging/windows/node-source.pin b/packaging/windows/node-source.pin index 6b34aaf1..846ac7cb 100644 --- a/packaging/windows/node-source.pin +++ b/packaging/windows/node-source.pin @@ -1 +1 @@ -21d4c73c6ce32fcbd68391968e85827339a511c0 +89dfcb95be5ace1a2b7a4fb18d88aeb22023cab4