Repository navigation
docs: name the run-failure catalog by its own name; move a test glob off the build path - #368
Merged
Merged
Conversation
The run-failure header and the two comment strings in the catalog generator named the catalog by its build-directory path; they now name it as run_failure_codes.json. The generator was re-run and include/pineforge/run_failure_codes.hpp and src/run_failure_registry.inc carry the new banner; their diff is banner lines only. The tutorial's run_error docstring describes the decision's owner by role instead of by script name. No code path changes: the catalog is still opened at docker/run_failure_codes.json.
Six comment-only files carried out of an earlier change so they do not wait for it: .gitignore, CMakeLists.txt, scripts/run_strategy.py, scripts/symbol_calendar.py, scripts/verify_corpus.py and src/ta_extremes_volume.cpp. Each edit is a comment, a docstring or a label; no statement, argument, path or default changes.
…ke file The file(GLOB ...) that discovers the generated refused_*.cpp fixtures now lives in tests/confirmed_capabilities_refusals.cmake and is included from runner/CMakeLists.txt at the position it held before, inside the same guard. Variable name, glob pattern and ordering are unchanged, so the same sources register in the same order.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Comment, banner and docstring text only; no behaviour change.
include/pineforge/run_failure.hpp,scripts/check_run_failure_codes.py(the generator banner, therender_codes_headercomment, and the module docstring at line 4), and the generatedinclude/pineforge/run_failure_codes.hppandsrc/run_failure_registry.inc, name the run-failure catalog by its own file name instead of by a directory path. The path the code actually opens is unchanged.tutorial/run.pydescribes the release harness by its role rather than by a file path..gitignore,CMakeLists.txt,scripts/run_strategy.py,scripts/symbol_calendar.py,scripts/verify_corpus.py,src/ta_extremes_volume.cpp.file(GLOB ... refused_*.cpp)discovery moves into a newtests/confirmed_capabilities_refusals.cmake, included fromrunner/CMakeLists.txtat the same position, inside the same guard, with the same variable name, the same pattern and the same order.What proves it
64 codes, registry in sync, 70 files scanned for uncoded throws, OK.Remote verification
rj-20261011t061212-69b0c6on this tree (520f75684, tree235043d0): preflight, release, debug, sanitizers, kernel, docs - all six exit 0.🤖 Generated with Claude Code