Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reel_board: tests/benchmarks/latency_measure/ fails #30513

Closed
s-kelvin opened this issue Dec 8, 2020 · 1 comment
Closed

reel_board: tests/benchmarks/latency_measure/ fails #30513

s-kelvin opened this issue Dec 8, 2020 · 1 comment
Labels
bug The issue is a bug, or the PR is fixing a bug

Comments

@s-kelvin
Copy link
Collaborator

s-kelvin commented Dec 8, 2020

Describe the bug
Running tests/benchmarks/latency_measure on reel board. The testcase benchmark.kernel.latency failed without any output.

To Reproduce
Steps to reproduce the behavior:

  1. west build -p auto -b reel_board tests/benchmarks/latency_measure/
  2. west flash

Expected behavior
Test should pass.

Impact
Test suite fails.

Logs and console output

*** Booting Zephyr OS build zephyr-v2.4.0-2092-g748e7b6d7515  ***
START - Time Measurement
Timing results: Clock frequency: 64 MHz

Environment (please complete the following information):

  • OS: Linux Ubuntu 18.04.4 LTS
  • Toolchain Zephyr SDK 0.11.2
  • Zephyr version zephyr-v2.4.0-2092-g748e7b6d7515
@s-kelvin s-kelvin added the bug The issue is a bug, or the PR is fixing a bug label Dec 8, 2020
@nashif
Copy link
Member

nashif commented Dec 15, 2020

cant reproduce:

DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v2.4.0-2426-gbca754569f2d  ***
DEBUG   - DEVICE: START - Time Measurement
DEBUG   - DEVICE: Timing results: Clock frequency: 64 MHz
DEBUG   - DEVICE: Average thread context switch using yield                   :     370 cycles ,     5792 ns
DEBUG   - DEVICE: Average context switch time between threads (coop)          :     376 cycles ,     5890 ns
DEBUG   - DEVICE: Switch from ISR back to interrupted thread                  :     533 cycles ,     8328 ns
DEBUG   - DEVICE: Time from ISR to executing a different thread               :     448 cycles ,     7000 ns
DEBUG   - DEVICE: Time to create a thread (without start)                     :     224 cycles ,     3500 ns
DEBUG   - DEVICE: Time to start a thread                                      :     406 cycles ,     6343 ns
DEBUG   - DEVICE: Time to suspend a thread                                    :     448 cycles ,     7000 ns
DEBUG   - DEVICE: Time to resume a thread                                     :     954 cycles ,    14906 ns
DEBUG   - DEVICE: Time to abort a thread (not running)                        :     263 cycles ,     4109 ns
DEBUG   - DEVICE: Average semaphore signal time                               :     144 cycles ,     2251 ns
DEBUG   - DEVICE: Average semaphore test time                                 :      68 cycles ,     1063 ns
DEBUG   - DEVICE: Semaphore take time (context switch)                        :     523 cycles ,     8171 ns
DEBUG   - DEVICE: Semaphore give time (context switch)                        :     700 cycles ,    10937 ns
DEBUG   - DEVICE: Average time to lock a mutex                                :      85 cycles ,     1328 ns
DEBUG   - DEVICE: Average time to unlock a mutex                              :     305 cycles ,     4768 ns
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL

@nashif nashif closed this as completed Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

No branches or pull requests

2 participants