aboutsummaryrefslogtreecommitdiff
path: root/tests/check_cli.py
diff options
context:
space:
mode:
authorOnur Gündüz <ogunduz@gmail.com>2026-06-21 08:42:10 +0200
committerOnur Gündüz <ogunduz@gmail.com>2026-06-21 08:42:10 +0200
commit7a047fd8f0c0f56143b7bb08aa326568abbc2284 (patch)
tree80b7f0f678de5d85aceaede40c223c911d773c2d /tests/check_cli.py
parentbe5ce08004c640aa5e77cf6155af3d124c66cf3e (diff)
downloadffwd-7a047fd8f0c0f56143b7bb08aa326568abbc2284.tar.gz
ffwd-7a047fd8f0c0f56143b7bb08aa326568abbc2284.zip
tests: point check scripts at the root ffwd-cli/ffwd-server symlinks
Diffstat (limited to 'tests/check_cli.py')
-rwxr-xr-xtests/check_cli.py8
1 files changed, 4 insertions, 4 deletions
diff --git a/tests/check_cli.py b/tests/check_cli.py
index 3044637..089ad95 100755
--- a/tests/check_cli.py
+++ b/tests/check_cli.py
@@ -7,7 +7,7 @@ runs a hermetic synthetic model (written by the gen_fixture test helper, the
same fixture the C tests build) so the CLI has something to load, then drives
the binary through its modes and asserts only exit codes and output shapes.
-The binary path is an argument (default tools/cli/ffwd-cli), so this works
+The binary path is an argument (default ./ffwd-cli), so this works
against any backend build - CPU, MLX, or CUDA. Backend-specific checks (the CPU
thread-count line) are gated on the binary's reported backend.
@@ -77,12 +77,12 @@ def backend_label(binary):
def main():
ap = argparse.ArgumentParser()
- ap.add_argument("--bin", default=os.path.join(ROOT, "tools", "cli", "ffwd-cli"),
- help="path to the embed CLI binary")
+ ap.add_argument("--bin", default=os.path.join(ROOT, "ffwd-cli"),
+ help="path to the ffwd CLI binary")
args = ap.parse_args()
binary = args.bin
- ensure_tool(binary, "tools/cli", "all")
+ ensure_tool(binary, ".", "cpu")
gen = os.path.join(ROOT, "tests", "gen_fixture")
ensure_tool(gen, "tests", "gen_fixture")