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

dangernoodle-io / breadboard / 30730519955
97%

Build:
DEFAULT BRANCH: main
Ran 02 Aug 2026 03:24AM UTC
Jobs 1
Files 214
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

02 Aug 2026 03:22AM UTC coverage: 96.84% (+0.002%) from 96.838%
30730519955

push

github

web-flow
fix: propagate bb_health section registration failures instead of discarding them (#1196)

bb_mqtt_client_health_register() and bb_temp_register_info() were both
void, discarding bb_health_section_register()'s bb_err_t with no log at
the call site. Their *_autoregister_init() wrappers additionally
hardcoded 'return BB_OK' regardless of the inner outcome. On the
bench, both producers failed with 'registry is frozen' and /api/health
kept returning 200 with zero section keys -- a degraded board looked
healthy.

Follows the pattern established by B1-1354 (PR #1187): change the
signature from void to bb_err_t and log (bb_log_e) at the call site on
failure, naming the specific section. The two *_autoregister_init()
wrappers now return their register function's real result instead of a
hardcoded BB_OK, so the existing aggregation in bb_app_init_rest()
(smoke) becomes live. floor_app.c's own return-value checks for these
two calls are dropped, not added to: the callee already logs the
failure by name, so a caller-side log would only repeat it; floor now
intentionally discards the two results (documented inline), same as it
and 8+ other in-tree call sites already discard bb_err_t returns
elsewhere with no compiler complaint (this repo has no
warn_unused_result anywhere) -- that gap is real and unaddressed here,
not retrofitted by this commit.

Host tests (test_bb_mqtt_client_health_section.c, test_bb_temp.c) force
bb_health_section_register() to fail via the existing
bb_health_section_freeze() seam and assert the error surfaces through
both the register and autoregister_init layers -- reverting the
propagation locally (both register functions and the mqtt wrapper) reproduces
the exact bug: three tests fail with BB_OK where BB_ERR_INVALID_STATE
was expected, restored after confirming.

B1-1370

8182 of 8746 branches covered (93.55%)

Branch coverage included in aggregate %.

11 of 11 new or added lines in 2 files covered. (100.0%)

13851 of 14006 relevant lines covered (98.89%)

2618.42 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30730519955.1 02 Aug 2026 03:24AM UTC 214
96.84
GitHub Action Run
Source Files on build 30730519955
  • Tree
  • List 214
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #30730519955
  • 0b1810a7 on github
  • Prev Build on main (#30730238004)
  • Next Build on main (#30732036197)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc