Recordsgolanggolang.org/x/sysfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×10
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-27
golang.org/x/sys/unix.Close golang.org/x/sys/unix.Getpid golang.org/x/sys/unix.NsecToTimeval golang.org/x/sys/unix.Pipe golang.org/x/sys/unix.Read golang.org/x/sys/unix.TimevalToNsec golang.org/x/sys/unix.Uname golang.org/x/sys/unix.Utsname golang.org/x/sys/unix.Write
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.48.0 PASS 26 passing observations
- v0.47.0 FAIL
- v0.46.0 PASS 36 passing observations
- v0.32.0 PASS 6 passing observations
- v0.31.0 FAIL
- v0.30.0 PASS 9 passing observations
- v0.29.0 FAIL
- v0.0.0-20220406155245-289d7a0edf71 FAIL
- v0.0.0-20181122145206-62eef0e2fa9b FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×6 2026-08-26 → 2026-08-27
- os=linux · runtime=go@1.26 ×4 2026-08-21 → 2026-08-26
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.0.0-20180830151530-49385e6e1522 → first failing release v0.0.0-20181122145206-62eef0e2fa9b
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.0.0-20181122145206-62eef0e2fa9b → first passing release v0.0.0-20190215142949-d0b11bdaac8a
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.0.0-20220310020820-b874c991c1a5 → first failing release v0.0.0-20220406155245-289d7a0edf71
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.0.0-20220406155245-289d7a0edf71 → first passing release v0.0.0-20220715151400-c0bba94af5f8
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.24.0 → first failing release v0.29.0
Releases between them never measured at this stage: 3
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.29.0 → first passing release v0.30.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.30.0 → first failing release v0.31.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v0.31.0 → first passing release v0.32.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.46.0 → first failing release v0.47.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.47.0 → first passing release v0.48.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No resolved dependency tree for v0.0.0-20180830151530-49385e6e1522 or for v0.0.0-20181122145206-62eef0e2fa9b, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/sys v0.47.0: windows.RtlGetNtVersionNumbers This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/windows.RtlGetNtVersionNumbers MIT-0 · 2026-08-18
- golang.org/x/sys v0.47.0: windows.CREATE_BREAKAWAY_FROM_JOB This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/windows.CREATE_BREAKAWAY_FROM_JOB MIT-0 · 2026-08-18
- golang.org/x/sys v0.47.0: registry.QUERY_VALUE This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/windows/registry.QUERY_VALUE MIT-0 · 2026-08-18
- golang.org/x/sys v0.31.0: unix.Write This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/unix.Write MIT-0 · 2026-08-30
- golang.org/x/sys v0.31.0: unix.Sysinfo_t This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/unix.Sysinfo_t MIT-0 · 2026-08-30
- golang.org/x/sys v0.31.0: unix.Sysinfo This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sys/unix.Sysinfo MIT-0 · 2026-08-30