CodeSampleX

Recordsgolanggolang.org/x/netfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×6

go: build output <str> already exists and is a directory

Evidence quality: complete · go · unclassified-diagnostic · outer go build · gap stage-unknown · First recorded: 2026-10-15 · Last seen: 2026-10-23

sha256:0882784d80c2…

golang.org/x/net/html.ElementNode golang.org/x/net/html.Node golang.org/x/net/html.NodeType golang.org/x/net/html.Parse golang.org/x/net/html.RawNode golang.org/x/net/html.Render golang.org/x/net/html.TextNode golang.org/x/net/html/atom.Atom golang.org/x/net/html/atom.Body golang.org/x/net/html/atom.Div golang.org/x/net/html/atom.Lookup golang.org/x/net/html/atom.Section golang.org/x/net/html/atom.String

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.

Where it reproduced

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.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 4 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

Published answers for the affected releases

Back to the package