diff --git a/esphome/analyze_memory/__init__.py b/esphome/analyze_memory/__init__.py index 5ef9eab526..3e85c4d869 100644 --- a/esphome/analyze_memory/__init__.py +++ b/esphome/analyze_memory/__init__.py @@ -294,24 +294,24 @@ class MemoryAnalyzer: # Try to find the appropriate c++filt for the platform cppfilt_cmd = "c++filt" - _LOGGER.warning("Demangling %d symbols", len(symbols)) - _LOGGER.warning("objdump_path = %s", self.objdump_path) + _LOGGER.info("Demangling %d symbols", len(symbols)) + _LOGGER.debug("objdump_path = %s", self.objdump_path) # Check if we have a toolchain-specific c++filt if self.objdump_path and self.objdump_path != "objdump": # Replace objdump with c++filt in the path potential_cppfilt = self.objdump_path.replace("objdump", "c++filt") - _LOGGER.warning("Checking for toolchain c++filt at: %s", potential_cppfilt) + _LOGGER.info("Checking for toolchain c++filt at: %s", potential_cppfilt) if Path(potential_cppfilt).exists(): cppfilt_cmd = potential_cppfilt - _LOGGER.warning("✓ Using toolchain c++filt: %s", cppfilt_cmd) + _LOGGER.info("✓ Using toolchain c++filt: %s", cppfilt_cmd) else: - _LOGGER.warning( + _LOGGER.info( "✗ Toolchain c++filt not found at %s, using system c++filt", potential_cppfilt, ) else: - _LOGGER.warning( + _LOGGER.info( "✗ Using system c++filt (objdump_path=%s)", self.objdump_path ) diff --git a/script/determine-jobs.py b/script/determine-jobs.py index bcc357d953..570b1a762c 100755 --- a/script/determine-jobs.py +++ b/script/determine-jobs.py @@ -26,7 +26,7 @@ The CI workflow uses this information to: - Skip or run Python linters (ruff, flake8, pylint, pyupgrade) - Determine which components to test individually - Decide how to split component tests (if there are many) -- Run memory impact analysis when components change +- Run memory impact analysis whenever there are changed components (merged config), and also for core-only changes Usage: python script/determine-jobs.py [-b BRANCH]