From 0b09e506854decd24b44a6ee77e2831f5a193859 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Fri, 17 Oct 2025 17:57:42 -1000 Subject: [PATCH] preen --- esphome/analyze_memory/cli.py | 4 ++-- script/determine-jobs.py | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/esphome/analyze_memory/cli.py b/esphome/analyze_memory/cli.py index 7b004353ec..bcf9f45de9 100644 --- a/esphome/analyze_memory/cli.py +++ b/esphome/analyze_memory/cli.py @@ -183,9 +183,9 @@ class MemoryAnalyzerCLI(MemoryAnalyzer): f"{len(symbols):>{self.COL_CORE_COUNT}} | {percentage:>{self.COL_CORE_PERCENT - 1}.1f}%" ) - # Top 10 largest core symbols + # Top 15 largest core symbols lines.append("") - lines.append("Top 10 Largest [esphome]core Symbols:") + lines.append("Top 15 Largest [esphome]core Symbols:") sorted_core_symbols = sorted( self._esphome_core_symbols, key=lambda x: x[2], reverse=True ) diff --git a/script/determine-jobs.py b/script/determine-jobs.py index 5767ced859..bcc357d953 100755 --- a/script/determine-jobs.py +++ b/script/determine-jobs.py @@ -13,9 +13,9 @@ what files have changed. It outputs JSON with the following structure: "component_test_count": 5, "memory_impact": { "should_run": "true/false", - "component": "component_name", - "test_file": "test.esp32-idf.yaml", - "platform": "esp32-idf" + "components": ["component1", "component2", ...], + "platform": "esp32-idf", + "use_merged_config": "true" } } @@ -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 exactly one component changes +- Run memory impact analysis when components change Usage: python script/determine-jobs.py [-b BRANCH]