Repository navigation
options: group A compile options have a fate; no burned-estate value newly refuses (Part of #4704) - #5477
Conversation
…ue newly refuses (Part of #4704) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
No description provided. |
|
PR #5477 @ 5b3a886: 2 failed check(s) == full-suite (failure) -- real == full-suite part 1/3 (failure) -- real |
|
No description provided. |
Part of #4704 (compiler-option rows, group A).
Group A's rows already exist on main (ZONEDATA/INVDATA refused by name #5088; TRUNC(OPT) #4746; ARITH(EXTEND) #5340; INTDATE(LILIAN) det port, oracle refuses by name). The issue's remaining check was the burned-estate "no recorded value newly refuses" test; this PR adds it, test-only.
Class table: ZONEDATA, INVDATA (refused by name), TRUNC(OPT), ARITH(EXTEND) (modelled, cobc runs STD/COMPAT with a det stop), INTDATE(LILIAN) (det port modelled, oracle refuses by name). Each has a fate and a C5 row, asserted.
Tests:
tests/cobol_mainframe/test_group_a_options.py(22; values cobc decides honoured; unhonourable refused by name; each of the 6 estate files' defaults, PARM and per-program overrides compile without a refusal and with no version conflict; every program card in the burned corpora raises no group-A refusal, skipped without corpora).Gates:
pr_gates --fast6/6; test_source_reads and option/estate tests pass. No golden, det or engine change.Cross-repo: none.
Co-Authored-By lines n/a.
🤖 Generated with Claude Code