igneum/tools/intel-arc

Intel Arc B580 on PC 1: the jobs (7 October 2026, branch intel-arc)

Plan: docs/plans/intel-arc.md. PC 1 (ae432dc7) is the project lead's desk: nothing here runs without his go for that run; every job is a signed run job through packaging/ota/publish-jobs.sh from the main checkout (its signer binary lives there), never pausing, resuming or quitting the installed app, never posting to api/cards (the RUNNER's --cards-off takes a card alone and restores it on any exit; tools/ci/playbook-quit-check.sh).

1. The driver (ran 7 October 2026)

pc1-intel-driver.ps1, elevated (one UAC prompt, the project lead's click), no --stop-miners. Downloads gfx_win_101.9034.exe from downloadmirror.intel.com/929959/ (932,631,144 bytes), checks the SHA512 Intel prints on page 785597 and the Authenticode signature, runs the installer with -s alone (silent, no -b: never reboots by itself), reads Intel's own logs under C:\ProgramData\Intel\GFXInstaller, then every adapter row, the PnP display devices, the class key's memory size and the installed worker's --list.

Run	Published	Outcome
run-ia-intel-driver-20261007	09:25:20Z	download 10 s, SHA512 equal, Authenticode "CN=Intel Corporation"; installer exit 1007 after 17 s: the bootstrapper wrapping the inner Installer.exe's exit 7 ("unsupported parameter", my -report <path>); no device check ran; the .NET Desktop Runtime it needs was installed (exit 0)
run-ia-intel-driver-20261007-b	09:43:59Z, the card in	-s alone; the report's lines are in the bench log entry

packaging/ota/publish-jobs.sh add --kind run --target ae432dc7 --id run-ia-intel-driver-<date>-<x> --elevated \
    --script tools/intel-arc/pc1-intel-driver.ps1 --timeout-minutes 60 --title "Intel Arc driver 32.0.101.9034 on PC 1" --deploy

2. The bench (published only on the project lead's go, after the card is in and the driver is on)

The kit first (packs only; the installed worker is the one under test):

tools/intel-arc/make-kit.sh "$TMPDIR/igneum-ia-arc-packs.zip"      # prints sha256 and bytes
packaging/ota/publish-jobs.sh add --kind fetch --target ae432dc7 --id fetch-ia-arc-packs-20261007 \
    --file "$TMPDIR/igneum-ia-arc-packs.zip" --dir jobs --extract --title "Intel Arc bench packs (class v4 and the v3 control)" --deploy

Then the bench, with the live network rate substituted (the consequences line's blocks a day) and the Arc's key for the runner's --cards-off (read it from the app's Cards page or api/state: on the 0.3.18 app the Arc is other:Intel(R) Arc(TM) B580 Graphics, on an app that carries this branch intel:Intel(R) Arc(TM) B580 Graphics; the runner matches the key with or without the device index, and both can be named):

NET=$(node -e "..." )   # live_state.hashes_per_second_estimate / 1e6, or read it from the observer (docs/plans/intel-arc.md section 5: 675 at 09:34Z on 7 October)
sed "s/__NETWORK_MHS__/$NET/" tools/intel-arc/pc1-arc-bench.ps1 > "$TMPDIR/ia-pc1-arc-bench.ps1"
packaging/ota/publish-jobs.sh add --kind run --target ae432dc7 --id run-ia-arc-bench-20261007 \
    --cards-off "other:Intel(R) Arc(TM) B580 Graphics,intel:Intel(R) Arc(TM) B580 Graphics" \
    --script "$TMPDIR/ia-pc1-arc-bench.ps1" --timeout-minutes 30 --title "Intel Arc B580: first light, memprobe, class v4 and v3 benches" --deploy

What it prints (node tools/jobs.mjs run-ia-arc-bench-20261007): RESULT list ... (the Intel OpenCL platform line), RESULT device <n> name= global_mib=, RESULT app_card key= vendor= kind= state= (read only), RESULT firstlight ... (the app's own worker line for the card), RESULT memprobe | chase | 1024 | ... (the dependent-load ceiling), RESULT G1 pack=v4-devnet-epoch0 fingerprint= match=yes|no (bit-exact on the fourth vendor), the same for the v3 control, the live pack and the --exchange local row, RESULT watts not-exposed source=IGCL..., then RESULT ROW ..., RESULT PICKER ['Intel Arc B580', <mhs>] (the site/yourcard.js entry, measured so it may go on the site) and RESULT CONSEQUENCES ... (the B580 owner's sentence), and a SUMMARY {json} line. About 3 to 5 minutes: the card switch up to 150 s, the memprobe under a minute, four benches of 5 dispatches of 2^24 (about 1 s each at 15 MH/s, plus IGC's compile of a few seconds per pack).

If OpenCL fails on the Arc the RESULT G1 ... error= and RESULT buildlog ... lines carry the compiler's exact words; the fallback order and hours are in the plan's section 4.

3. Dry run

The playbooks are PowerShell; this Mac has no pwsh (the Homebrew cask is gone from the tap and the Command Line Tools are too old for a cask install today), so the Mac-side dry run against the UI mock (node tools/ui-mock/server.mjs 4310 with ?scenario=intel, whose api/state carries the Intel row) is owed until a PowerShell is on the Mac (Microsoft's pkg, the project lead's word for the download). What stands in: the driver playbook ran live on PC 1 twice with the same helper shapes (Stamp, Summary, the adapter and worker-list readers), and the four CI checks pass on both scripts (kit-path-check, ps-drive-ref-check, kill-by-name-check, playbook-quit-check).