Recordsnpmelectron-to-chromiumfailure issue
Failure signature
UNKNOWN exit 2 Evidence gap ×1
flag provided but not defined: -e · usage: go run [build flags] [-exec xprog] package [arguments...] · Run <str> for details.
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-04 · Last seen: 2026-09-04
sha256:00e630595b1e…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 1.5.430 not measured
- 1.5.427 not measured
- 1.5.422 not measured
- 1.5.421 FAIL
- 1.5.420 not measured
- 1.5.419 not measured
- 1.5.418 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-04 → 2026-09-04
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.