-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esp32-fix-empty-logs(#35939) #35965
esp32-fix-empty-logs(#35939) #35965
Conversation
Review changes with SemanticDiff. |
PR #35965: Size comparison from 1dadbe4 to fc2305f Full report (88 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35965: Size comparison from a854245 to 7009b63 Full report (88 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Hi @mokap13, The earlier changes (#26348) were made with specific requirements in mind. The The log format consists of three parts:
We intentionally added the printf statements to ensure we could apply colors to logs redirected to the console while optimizing the usage of buffer. These changes were introduced in this PR. Given this context, I believe the change in #35965 should be reverted. |
This reverts commit 2a19f57.
* Revert "esp32-fix-empty-logs(project-chip#35939) (project-chip#35965)" This reverts commit 2a19f57. * Add comment explaining why printf is used
Fixes #35939
Replaced
printf
withesp_log_write
, that check log level