0b76fd92fc
There are instances where on hardware tests would result in multiple dictionary logging blocks. This is usually due to flashing and running via twister in separate steps. Once flashing is done, the device starts running and sending logging string to output, but twister is not ready to read them, thus leaving the strings in the host's UART buffer. Then twister starts its testing run by resetting the device which results in another dictionary logging block to show up. So the pytest script has to be updated to only look at the last dictionay logging block. Signed-off-by: Daniel Leung <daniel.leung@intel.com> |
||
|---|---|---|
| .. | ||
| dictionary | ||
| log_api | ||
| log_backend_fs | ||
| log_backend_init | ||
| log_backend_uart | ||
| log_benchmark | ||
| log_blocking | ||
| log_cache | ||
| log_core_additional | ||
| log_custom_header | ||
| log_immediate | ||
| log_link_order | ||
| log_links | ||
| log_msg | ||
| log_output | ||
| log_stack | ||
| log_stress | ||
| log_switch_format | ||
| log_syst | ||
| log_timestamp | ||