Recordsgolanggolang.org/x/sysfailure issue
Failure signature
PROJECT_TEST ESM Evidence gap ×311
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-15 · Last seen: 2026-10-18
golang.org/x/sys/windows.CREATE_BREAKAWAY_FROM_JOB golang.org/x/sys/windows.CREATE_NEW_PROCESS_GROUP golang.org/x/sys/windows.CloseHandle golang.org/x/sys/windows.CreateFile golang.org/x/sys/windows.DELETE golang.org/x/sys/windows.DETACHED_PROCESS golang.org/x/sys/windows.ERROR_ACCESS_DENIED golang.org/x/sys/windows.ERROR_DELETE_PENDING golang.org/x/sys/windows.ERROR_FILE_NOT_FOUND golang.org/x/sys/windows.ERROR_INVALID_PARAMETER golang.org/x/sys/windows.ERROR_PATH_NOT_FOUND golang.org/x/sys/windows.FILE_ATTRIBUTE_NORMAL golang.org/x/sys/windows.FILE_ATTRIBUTE_REPARSE_POINT golang.org/x/sys/windows.FILE_FLAG_OPEN_REPARSE_POINT golang.org/x/sys/windows.FILE_SHARE_DELETE golang.org/x/sys/windows.FILE_SHARE_READ golang.org/x/sys/windows.FILE_SHARE_WRITE golang.org/x/sys/windows.FileAttributeTagInfo golang.org/x/sys/windows.FileDispositionInfo golang.org/x/sys/windows.GENERIC_READ golang.org/x/sys/windows.GetExitCodeProcess golang.org/x/sys/windows.GetFileInformationByHandleEx golang.org/x/sys/windows.Handle golang.org/x/sys/windows.OPEN_EXISTING golang.org/x/sys/windows.OpenProcess golang.org/x/sys/windows.PROCESS_QUERY_LIMITED_INFORMATION golang.org/x/sys/windows.RtlGetNtVersionNumbers golang.org/x/sys/windows.SetFileInformationByHandle golang.org/x/sys/windows.UTF16PtrFromString golang.org/x/sys/windows/registry.LOCAL_MACHINE golang.org/x/sys/windows/registry.OpenKey golang.org/x/sys/windows/registry.QUERY_VALUE
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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 1 passing observations
- v0.47.0 FAIL
- v0.45.0 FAIL
- v0.44.0 PASS 3 passing observations
- v0.42.0 PASS 143 passing observations
- v0.41.0 FAIL
- v0.40.0 PASS 2 passing observations
- v0.32.0 PASS 3 passing observations
- v0.31.0 FAIL
- v0.30.0 FAIL
- v0.29.0 PASS 6 passing observations
- v0.28.0 FAIL
- v0.27.0 PASS 6 passing observations
- v0.18.0 FAIL
- v0.10.0 FAIL
- v0.0.0-20220406155245-289d7a0edf71 FAIL
Where it reproduced
- os=windows · runtime=go@1.26 ×303 2026-08-15 → 2026-10-18
- executionContext=go · os=linux · runtime=go@1.26 ×4 2026-08-30 → 2026-09-07
- os=linux · runtime=go@1.26 ×4 2026-08-26 → 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-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.9.0 → first failing release v0.10.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.10.0 → first passing release v0.11.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.17.0 → first failing release v0.18.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.18.0 → first passing release v0.19.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.27.0 → first failing release v0.28.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.28.0 → first passing release v0.29.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release v0.29.0 → first failing release v0.30.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.40.0 → first failing release v0.41.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v0.41.0 → first passing release v0.42.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last passing release v0.44.0 → first failing release v0.45.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-20220310020820-b874c991c1a5 or for v0.0.0-20220406155245-289d7a0edf71, 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.45.0: unix.ByteSliceToString, unix.NsecToTimespec, unix.TimespecToNsec 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.ByteSliceToStringgolang.org/x/sys/unix.NsecToTimespecgolang.org/x/sys/unix.TimespecToNsecgolang.org/x/sys/unix.Getpagesize MIT-0 · 2026-08-18
- golang.org/x/sys v0.41.0: unix.O_RDONLY 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.O_RDONLYgo 1.26.6 MIT-0 · 2026-09-04
- golang.org/x/sys v0.41.0: unix.Stat_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.Stat_t MIT-0 · 2026-09-04