CodeSampleX

Recordsgolanggolang.org/x/textfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×2

go: cannot run *_test.go files (contract_test.go)

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-07 · Last seen: 2026-09-20

sha256:1f0f73f78ab5…

golang.org/x/text/language.Afrikaans golang.org/x/text/language.AmericanEnglish golang.org/x/text/language.BrazilianPortuguese golang.org/x/text/language.BritishEnglish golang.org/x/text/language.Comprehends golang.org/x/text/language.Danish golang.org/x/text/language.Dutch golang.org/x/text/language.English golang.org/x/text/language.EuropeanPortuguese golang.org/x/text/language.French golang.org/x/text/language.German golang.org/x/text/language.Italian golang.org/x/text/language.Low golang.org/x/text/language.Norwegian golang.org/x/text/language.Portuguese golang.org/x/text/language.Russian golang.org/x/text/language.Spanish golang.org/x/text/language.Swedish golang.org/x/text/language.Tag golang.org/x/text/language.Ukrainian golang.org/x/text/language.Und

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: 2 · unchanged at every release: 1

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