- LongPath.expected: revert wrong rebless from 69c27c53c1b. CI generates
the long-path file during build, so the long-path entry is correct.
- 4 framework/query DataFlowConsistency.expected: pure toString polish
(ControlFlowNode for X -> X / After X).
- essa/ssa-compute/CONSISTENCY/TypeTrackingConsistency.expected: deleted.
The 6 prior 'unreachable node in step of kind ...' violations are gone
under the new SSA; per CI auto-rebless convention the empty file is
removed.
- extractor-tests/syntax_error/CONSISTENCY/CfgConsistency.expected: new.
Documents one expected deadEnd on `break` outside any loop in the
syntax-error test corpus.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Observed on some test files in Nuitka/Nuitka, having `break` and
`continue` outside of loops in Python is (to Python) a syntax error, but
our parser happily accepted this broken syntax.
This then caused issues further downstream in the control-flow
construction, as it broke some invariants.
To fix this we now skip the code that would previously fail when the
invariants are broken.
Co-authored-by: yoff <yoff@github.com>