Repository navigation
CI never runs Go's stub-backed public-API tests (TestStub*, TestRegistry*): they skip by name everywhere #463
Description
Activity
- added a commit that references this issue
on Oct 6, 2026 Fixed by #465, merged into
v1and part of the 1.0.2 release.Go's conformance leg now runs the whole Go suite with the stub libraries set and the race detector on. A census reads the verdict and fails on:
- a zero-run;
- any test that skips for the stub gate while the stubs are set;
- a missing required test.
measuredin both Go legs: 278 passed, 0 failed, with the 15TestStub*, 3TestRegistry*and the setup case all run. The Python, TypeScript and Rust scripts already ran all their stub-gated tests, and now share the same census guard.🤖 Generated with Claude Code
No CI job runs Go's stub-backed public-API tests. They skip by name in every run, so nothing would catch a regression in them.
measuredfrom the scripts and workflows onv1:gojob inci.ymlruns the Go suite with no stub library, so every stub-backed test skips by name: 36 skips in the latest census, among them the 13TestStub*tests ingo/chtypes/stub_test.goand theTestRegistry*tests ingo/chtypes/adapter_test.go.v1-abi.ymldoes build the stubs and setsCHTYPES_ABI1_STUBS. But for Go it runsscripts/abi-v1/conformance/go.sh, and that script runs onlygo test ./internal/abi1/... -run TestConformanceandgo test ./chtypes -run TestGoldensV1StubSelfCheck(plus, once the setup-latch change lands,TestSetupCases).TestStub*andTestRegistry*run only when someone setsCHTYPES_ABI1_STUBSlocally. They pass when run that way (measuredlocally with stubs).Fix:
scripts/abi-v1/conformance/go.shrunsgo test ./chtypes -count=1in full with the stubs set, and reads its verdict from the test census the same waycheck-standalone.shdoes, so a zero-run fails.Also check: whether the Python, TypeScript and Rust conformance scripts have the same gap for their stub-backed public tests. That is
unverified; only Go was read.🤖 Generated with Claude Code