Frdm_k64f samples/drivers/can/counter/ fails. #57654
Description
Describe the bug
This sample failed because of a timeout at the regex expectation.
The sample.yml defines the regex value as Counter received: (.*)
In the README file, we can read that the output should be like this:
Sample output
=============
.. code-block:: console
Change LED filter ID: 0
Finished init.
Counter filter id: 4
uart:~$ Counter received: 0
Counter received: 1
Counter received: 2
Counter received: 3
It looks like it needs to have add-on external uart converter from frdm board to the testing host?
According to the handler.log file, there is only this part of sample output.
Change LED filter ID: 0
Finished init.
Counter filter id: 1
There is no Counter received: (.*) value (at the main communication port).
This can be a reason for failing (timeout).
To Reproduce
twister --device-testing --hardware-map <path_to>/map.yml -T ./samples/drivers/can/counter/ -v
Expected behavior
Getting Counter received: (.*) for regex expectation.
Impact
Annoyance.
Logs and console output
Renaming output directory to <path_to>/twister-out.10
INFO - Using Ninja..
INFO - Zephyr version: zephyr-v3.3.0-3578-g1f43e126a841
INFO - Using 'zephyr' toolchain.
INFO - Building initial testsuite list...
INFO - Writing JSON report <path_to>/twister-out/testplan.json
Device testing on:
| Platform | ID | Serial device |
|------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------|
| frdm_k64f | 02400b0132044e4500417009997b00316781000097969900 | /dev/serial/by-id/usb-ARM_DAPLink_CMSIS-DAP_02400b0132044e4500417009997b00316781000097969900-if01 |
| frdm_k64f | 02400b0140214e45001b1018c89200349e11000097969900 | /dev/serial/by-id/usb-ARM_DAPLink_CMSIS-DAP_02400b0140214e45001b1018c89200349e11000097969900-if01 |
INFO - JOBS: 8
INFO - Adding tasks to the queue...
INFO - Added initial list of jobs to queue
INFO - 1/1 frdm_k64f samples/drivers/can/counter/sample.drivers.can.counter FAILED Timeout (device 64.157s)
ERROR - see: <path_to>/twister-out/frdm_k64f/samples/drivers/can/counter/sample.drivers.can.counter/handler.log
INFO - 1 test scenarios (1 test instances) selected, 0 configurations skipped (0 by static filter, 0 at runtime).
INFO - 0 of 1 test configurations passed (0.00%), 1 failed, 0 errored, 0 skipped with 0 warnings in 69.52 seconds
INFO - In total 1 test cases were executed, 0 skipped on 1 out of total 567 platforms (0.18%)
INFO - 1 test configurations executed on platforms, 0 test configurations were only built.
Hardware distribution summary:
| Board | ID | Counter |
|-----------|--------------------------------------------------|-----------|
| frdm_k64f | 02400b0132044e4500417009997b00316781000097969900 | 1 |
| frdm_k64f | 02400b0140214e45001b1018c89200349e11000097969900 | 0 |
INFO - Saving reports...
INFO - Writing JSON report <path_to>/twister-out/twister.json
INFO - Writing xunit report <path_to>/twister-out/twister.xml...
INFO - Writing xunit report <path_to>/twister-out/twister_report.xml...
INFO - -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
INFO - The following issues were found (showing the top 10 items):
INFO - 1) samples/drivers/can/counter/sample.drivers.can.counter on frdm_k64f failed (Timeout)
INFO -
INFO - To rerun the tests, call twister using the following commandline:
INFO - west twister -p <PLATFORM> -s <TEST ID>, for example:
INFO -
INFO - west twister -p frdm_k64f -s samples/drivers/can/counter/sample.drivers.can.counter
INFO - or with west:
INFO - west build -p -b frdm_k64f -T samples/drivers/can/counter/sample.drivers.can.counter
INFO - -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
INFO - Run completed
Environment (please complete the following information):
- OS: Linux
- Toolchain: Zephyr SDK 0.16.0
- West version: v0.13.1
- Latest main: 84ba03a