From d62df9ad15d126e840d3e98c4c8134af0c63dbf7 Mon Sep 17 00:00:00 2001 From: Oleksandr Bezdieniezhnykh Date: Mon, 18 May 2026 07:46:44 +0300 Subject: [PATCH] [AZ-615] run-tests-jetson: BSD rsync compat (no --info=progress2) macOS ships BSD rsync, which doesn't support GNU's --info=progress2. Drop the flag (added --stats so we still get a summary at the end) and document the LFS-pointer pre-smudge requirement that bit during the first end-to-end attempt. Co-authored-by: Cursor --- scripts/run-tests-jetson.sh | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/scripts/run-tests-jetson.sh b/scripts/run-tests-jetson.sh index 5f75b89..cbe6fcf 100755 --- a/scripts/run-tests-jetson.sh +++ b/scripts/run-tests-jetson.sh @@ -67,11 +67,18 @@ echo "[run-tests-jetson] compose file: ${COMPOSE_FILE}" # * .DS_Store — macOS metadata # * *.tlog / *.bin / *.engine — large fixtures that exist on Jetson # either via a separate fixture-sync step or are produced by the SUT -# Git LFS pointers (134 B files) DO transfer — they're text. The -# Jetson runs `git lfs pull` lazily for any LFS-tracked fixture it -# actually needs. +# Note on LFS-tracked fixtures (e.g. flight_derkachi.mp4): Git LFS +# pointers (134-byte text files) transfer fine, but the SUT needs the +# real binary. The convention on the Mac side is to smudge the pointer +# locally BEFORE running this script (e.g. `git lfs pull`, or copy +# from `.git/lfs/objects//...`). rsync then transfers the actual +# bytes. If a fixture arrives as a pointer the test will fail-fast +# with "Derkachi fixture missing". +# +# Flags note: macOS ships BSD rsync, which doesn't support GNU's +# `--info=progress2`. Stick to the portable subset. echo "[run-tests-jetson] rsync → ${SSH_ALIAS}:${REMOTE_DIR}/" -rsync -avz --delete \ +rsync -az --delete --stats \ --exclude=.git/ \ --exclude='__pycache__/' \ --exclude='*.pyc' \