1
0
mirror of https://github.com/esphome/esphome.git synced 2025-10-21 03:03:50 +01:00

Merge remote-tracking branch 'origin/ci_impact_analysis' into ci_impact_analysis

This commit is contained in:
J. Nick Koston
2025-10-17 17:58:05 -10:00
2 changed files with 7 additions and 7 deletions

View File

@@ -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
)

View File

@@ -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]