sascha/esphome
1
0
Fork 0
mirror of https://github.com/esphome/esphome.git synced 2025-10-21 19:23:45 +01:00
Code Issues Releases Wiki Activity

preen

Browse Source
This commit is contained in:
J. Nick Koston
2025-10-17 17:57:42 -10:00
parent c70937ed01
commit 0b09e50685
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
esphome/analyze_memory/cli.py
View File

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

8
script/determine-jobs.py
View File

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