[gareth-morgan-nv]

Summary

Two development tools for argus_sender that the runtime does not depend on: cross_build.sh to type-check and cross-compile on an x86 PC, and deploy_sender.py to build and try a release on a Jetson without activating it.

What changed

• cross_build.sh syntax runs clang over every sender source against an Orin sysroot (no linking); cross_build.sh build [cmake args] builds an aarch64 argus_sender with the Arm toolchain (linked, not run). The sysroot, toolchain and CMake toolchain file live under ORIN_CROSS_ROOT; the script header lists what they must contain, and TESTING.md gets a short section.
• deploy_sender.py:
  • check and discover only read (release, camera processes, disk, platform files, camera units).
  • deploy [--with-sipl] --name N copies the committed source (a git archive of HEAD) into a new ~/camera-streamer/releases/N, builds it on the target and runs the camera-free unit tests. It refuses an existing release name and a tree with uncommitted changes, and a failing unit test fails the deploy.
  • run --name N --config FILE [--seconds S] [--env NAME=VALUE] starts a built release for a bounded time. It prints a note, and stops nothing, if another camera process is running. It succeeds when the sender ends at its time limit and otherwise fails with the sender's exit status.
  • stop signals the senders that run started; linktest measures TCP throughput from the target to the desktop.
  • It never stops, replaces or starts a service.

Validation

• pre-commit (REUSE, ruff, ruff format) clean on the script; --dry-run check prints the ssh commands without running them.
• cross_build.sh syntax and build (with -DWITH_SIPL=ON and OFF) pass on a combined local build of the sender PRs, and earlier on this script alone. The plain base does not compile bundle_assembler without the Argus headers, so the script is meant for Orin-targeted trees.
• deploy_sender.py was used for the native builds, unit-test runs and camera runs on a Jetson Orin behind the sender PRs: check, deploy --with-sipl (17 of 17 tests), run, stop and linktest.
• The failure paths (a failing unit test, a sender that exits with an error) are read and dry-run but not exercised on a target.

Known limitations / follow-ups

• A sender ended with stop is reported as "exited with status 1"; the script does not yet separate a signal stop from an error.
• Tests that include Argus headers compile through cross_build.sh but run only on a Jetson.

Test plan

• deploy_sender.py user@board check, then deploy into a new release name.
• cross_build.sh syntax against your own Orin sysroot.
• CI.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: NVIDIA/IsaacCapture
• Branch: teng/5ef2afa
• File: .coderabbit.yaml
• Commit: afdf8e8
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 772d6594-c65c-4413-8df6-65f2c61c801a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts