Skip to content

Fix Makefile and documentation paths left behind by moved files - #4166

Open
DanielMBouyou wants to merge 1 commit into
openvinotoolkit:developfrom
DanielMBouyou:fix-stale-paths-after-tools-reorg
Open

Fix Makefile and documentation paths left behind by moved files#4166
DanielMBouyou wants to merge 1 commit into
openvinotoolkit:developfrom
DanielMBouyou:fix-stale-paths-after-tools-reorg

Conversation

@DanielMBouyou

@DanielMBouyou DanielMBouyou commented Aug 9, 2026

Copy link
Copy Markdown

Changes

Repoint five references left pointing at files that were renamed or removed by merged refactors:

  • Makefile, test-fuzz — invoked quantize_api.py; Rework fuzzing tests #3695 removed it and added fuzz_target.py in the same commit. Filename only: both call atheris.Setup(sys.argv, ...), behaviour unchanged.
  • Makefile, install-openvino-dev — installs from openvino/yolov8/, renamed yolo26 in [OpenVINO] YOLO26 sample #3844.
  • docs/usage/IgnoredScope.md, tests/post_training/README.md, a --memory-monitor help string — tools/ paths moved in Reorganization tools directory  #3939. render_dot_to_svg.py takes -i, not -m.

Adds tests/docs/test_makefile_paths.py: scripts named in Makefile recipes must exist.

install-models-hub-torch installs from tests/torch/models_hub_test/, deleted in #3553; removing a target seemed like your call.

Reason for changes

make test-fuzz fails on its only line; make install-openvino-dev on its third, a requirements file that no longer exists. No CI job runs the fuzz target, so nothing caught it.

Related tickets

None; no issue or PR covers these paths.

Tests

Test fails on develop naming Makefile:166, passes after. pytest tests/docs green (14), tests/common unchanged, Ruff v0.15.18 check and format clean. The memory_monitor edits are text, checked by inspection.

Five references still point at files that were moved or renamed by
merged pull requests, and nothing in CI notices, because no test
asserts that a path named in the build or the docs resolves.

Makefile, test-fuzz: invoked tests/cross_fw/sdl/fuzz/quantize_api.py,
removed in openvinotoolkit#3695, which added fuzz_target.py in the same commit. The
filename is the only change; both scripts call atheris.Setup(sys.argv,
...) and then atheris.Fuzz(), so argument handling and behaviour are
unchanged. This target is the only invocation of the fuzz target in
the repository, so no CI job caught the breakage.

Makefile, install-openvino-dev: installed from
examples/post_training_quantization/openvino/yolov8/, renamed to
yolo26 in openvinotoolkit#3844.

docs/usage/IgnoredScope.md, tests/post_training/README.md and the
--memory-monitor help text in tests/post_training/conftest.py: tools/
paths moved in openvinotoolkit#3939. The documented render_dot_to_svg command also
passed -m, which the script does not register; its parser accepts -i
and --input_file.

Adds tests/docs/test_makefile_paths.py, asserting that Python scripts
written out literally in Makefile recipes exist. It is deliberately
narrow: it does not cover requirements files, paths built from Make
variables, or python -m invocations, so a green run is not a claim
that every target works.

install-models-hub-torch is left alone. It installs from
tests/torch/models_hub_test/, deleted in openvinotoolkit#3553, and the only repair
is removing the target, which is a maintainer's decision.
@DanielMBouyou
DanielMBouyou requested a review from a team as a code owner August 9, 2026 14:14
@github-actions github-actions Bot added documentation Improvements or additions to documentation NNCF PTQ Pull requests that updates NNCF PTQ labels Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation NNCF PTQ Pull requests that updates NNCF PTQ

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant