boot_test_parser: fix exception pattern without kernel timestamps
The exception multiline pattern was failing to match kernel exception messages in logs that only contained syslog priority tags without kernel timestamps. This affected embedded systems like qemu-armv5 where logs appear as:
<4>------------[ cut here ]------------ <1>8<--- cut here ---
instead of the typical timestamped format:
[ 123.456789] ------------[ cut here ]------------
Updated the pattern to use more flexible matching that captures all four common "cut here" formats:
- Syslog priority only: <4>------------[ cut here ]------------
- Syslog with unusual prefix: <1>8<--- cut here ---
- Kernel timestamp only: [ 123.456789] ------------[ cut here ]------------
- Combined format: <4>[ 123.456789] ------------[ cut here ]------------
Added test with all four formats to prevent regression.
Reported-by: Katie Worton katie.worton@linaro.org Signed-off-by: Anders Roxell anders.roxell@linaro.org