add timestamp to UART Logs
The UART log in the test report & JSON report are great, but they are generally disconnected from the step results.
It would be really helpful to have a timestamp for each line using the same clock as the steps report.
-
Official comment
We might be able add some form of timestamps for UART (and CAN) logs, but due to the asynchronous nature of UART/CAN (and buffering in multiple layers), these will always be somewhat skewed from the test execution clock used in the steps report. For this reason, CAN and UART logs are included outside the scope of an individual step result in the JSON file.
We could consider to include timestamps in the report for when a data chunk is dequeued from the PLT's controller, or injected into the PLT's controller, but this will not be the exact timestamp that data chunk is communicated by the USB-CDC UART adapter actually performing the UART communication with the DUT.
Comment actions
Please sign in to leave a comment.
Comments
2 comments