Skip to content

test: enable high-verbosity logging in every component test config - #316

Merged
eigger merged 1 commit into
masterfrom
test/strengthen-logger-coverage
Aug 18, 2026
Merged

test: enable high-verbosity logging in every component test config#316
eigger merged 1 commit into
masterfrom
test/strengthen-logger-coverage

Conversation

@eigger

@eigger eigger commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • fix: ESPBTUUID::to_str() requires a buffer argument, not zero #315 fixed a build break that only surfaced in production, not in CI, because no component test config declares a logger: component — ESPHome silently strips ESP_LOGCONFIG/ESP_LOGW calls down to no-ops in that case and never type-checks their arguments. This PR closes that gap so it can't happen again.
  • Adds logger: level: VERY_VERBOSE to every component's test config (in the shared common.yaml/common_rx_features.yaml where one exists, so all variants of a component inherit it in one place).
  • Recompiling everything with this change caught one more real bug it was hiding: a %u format specifier vs. uint32_t argument mismatch in divoom_display.cpp's dump_config() (same class of issue already fixed in ble_elm327 in fix: clean up build warnings and sync Colorado Tab5 package #314) — fixed here too.

Test plan

  • esphome compile for all 16 esp32-idf/esp32-ard test configs across every component — all Successfully compiled program., zero warnings in our code.

🤖 Generated with Claude Code

None of the component test configs declared a logger: component,
which makes ESPHome silently compile ESP_LOGCONFIG/ESP_LOGW down to
no-ops and skip type-checking their arguments entirely (see #315,
where this exact gap let a broken ESPBTUUID::to_str() call through
CI). Add logger: level: VERY_VERBOSE to every component's test config
(via the shared common.yaml where one exists) so dump_config() and
warning-log code paths actually get compiled and type-checked.

Recompiled every component's esp32-idf/esp32-ard test config with
this change and fixed the one warning it caught: a %u format
specifier vs. uint32_t argument mismatch in divoom_display.cpp's
dump_config(), the same class of bug already fixed in ble_elm327.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@eigger
eigger merged commit 6548842 into master Aug 18, 2026
30 checks passed
@eigger
eigger deleted the test/strengthen-logger-coverage branch August 20, 2026 03:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant