• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

nvidia-holoscan / holoscan-cli / 27202992953
77%
main: 77%

Build:
Build:
LAST BUILD BRANCH: release/4.3.0
DEFAULT BRANCH: main
Ran 09 Jun 2026 11:27AM UTC
Jobs 1
Files 35
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

04 Jun 2026 03:03PM UTC coverage: 77.152% (+0.9%) from 76.298%
27202992953

push

github

web-flow
Sync post-consolidation HoloHub CLI changes (#1576, #1582, #1587, #1596) (#180)

* Sync module operator_names field from HoloHub CLI (#1576)

HoloHub main renamed the cosmetic top-level module `operators` field to
`operator_names` and updated `list` to fall back across
operator_names -> operators -> subprojects.operators
(nvidia-holoscan/holohub#1576). That change landed after the CLI
consolidation snapshot, so port it into the standalone CLI:

- module.schema.json: rename `operators` -> `operator_names` and
  reclassify it as a display-only field (build gating stays on
  subprojects.operators).
- info.py handle_list: read the new field with backward-compatible
  fallbacks so existing metadata.json files still render.
- Update the module fixture and add fallback coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Sync package-command fixes from HoloHub CLI (#1582, #1596)

Port two post-consolidation HoloHub in-tree CLI fixes that the migration
PR drops along with the in-tree CLI:

- #1596: register `--no-docker-build` on `holoscan package`. handle_package
  already honored check_skip_builds(); the flag just wasn't exposed.
- #1582: in-tree module packaging needs BOTH `-DMODULE_<slug>=ON` (enter the
  module subdir via add_holohub_module) AND `-DPKG_<slug>=ON` (activate the
  add_holohub_package cascade that emits the CPack config). holoscan-cli
  emitted only one (PKG for standalone, MODULE for in-tree), so in-tree
  `holoscan package <name>` produced no package. Emit both unconditionally,
  matching the HoloHub CMake gating in HoloHubConfigHelpers.cmake.

#1597 (forwarding --cuda from `package` to the container build) was already
correct here; added a regression test to lock it in.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Wire external module-sites resolution into build (#1587)

holoscan-cli shipped the external_resolver + cmake_manifest library code but
never invoked it from the build fl... (continued)

64 of 69 new or added lines in 4 files covered. (92.75%)

1 existing line in 1 file now uncovered.

2958 of 3834 relevant lines covered (77.15%)

0.77 hits per line

Uncovered Changes

Lines Coverage ∆ File
5
95.93
-4.07% src/holoscan_cli/utils/external_resolver.py

Coverage Regressions

Lines Coverage ∆ File
1
86.81
1.35% src/holoscan_cli/commands/build.py
Jobs
ID Job ID Ran Files Coverage
1 27202992953.1 09 Jun 2026 11:27AM UTC 35
77.15
GitHub Action Run
Source Files on build 27202992953
  • Tree
  • List 35
  • Changed 4
  • Source Changed 4
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #27202992953
  • 7f4ffef5 on github
  • Prev Build on main (#26902082146)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc