1.6 KiB
Process run-2 preparation failure
These are the exact three files retained from
.local/process-multiselect-native/run-2: generation.json and its empty stdout
and stderr logs. Fixture generation exited 3221225781 (0xC0000135) before
preparation completed. There was no GUI launch, prepared.json, started.json or
finished.json. This is a failed preparation receipt, not a native run or a
failed complete-Project comparison.
The checker came from native-build-2, source commit
b743a10d51032dc1655b94fed5e49fbbbcee83f4. The parent diagnosed the omitted
toolchain runtime environment in its preparation shell; Windows reported the
missing-DLL status. The parent subsequently retried with that environment in
run-3 successfully. That diagnosis and retry outcome are parent observations;
the raw run-2 receipt records the exit code, executable/build pins and empty
streams, and does not record its environment or name a missing DLL. Run-3's
separate native evidence owns its acceptance claims.
Verify with Python's standard library, using the portable sibling checks:
python -B verify.py --checks ../checks
The verifier checks exact raw/outer bytes, failed generation command and
chronology, empty stream pins, and the checker's precise build receipt, input
map and Cargo executable/readback relationship. It also checks the shared
source map against the sibling source proof for b743a10. Run the checks and
source verifiers separately for their complete gate/source verification.
No binary, capture helper or GUI is executed. Pins establish consistency,
not independent authentication or a reproduction of the environment failure.