feat(logger): Update to use esp_log_timestamp so that timestamp value matches ESP_LOG timestamps
#570
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
loggerto useesp_log_timestamp()to retrive timestamp for logging on espressif platformsMotivation and Context
esp_logtimestamps were always greater by up to 1 second), which could lead to confusion when correlating log messages.How has this been tested?
Build and run the
logger/exampleon a QtPy ESP32-S3 board and verify that the logger timestamps match the esp_log timestamps.Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Types of changes
Checklist:
Software
.github/workflows/build.ymlfile to add my new test to the automated cloud build github action.