Conformance doc narrative contradicts the manifest #2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Status (2026-07-04)
Open. Documentation staleness, quick fix.
docs/YAML_TEST_SUITE_CONFORMANCE.mdstill says the suite stands at 329 passing with 73 gaps, while the machine-authoritativeTests/Fixtures/yaml-test-suite-manifest.yamlrecords 402 passing and 0 gaps on theconformance/yaml-test-suite-gapsbranch. The doc even contradicts itself: its intro says the gate now guards all 402 cases.Fix: rewrite the stale sections to match the manifest, and state explicitly that the manifest is the source of truth so the prose cannot silently rot again.
Fixed in
e76472donconformance/yaml-test-suite-gaps: headline updated to 402 passing / 0 gap, the manifest named as source of truth over the prose, the remaining-gaps narrative retired, bucket 6 marked done, and a closing section added recording the libyaml-port cutover and the final fix series. Closing since the doc and manifest live on the same branch and now agree.