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

intermittent failure in tests/benchmarks/timing_info #13073

Closed
andrewboie opened this issue Feb 5, 2019 · 1 comment
Closed

intermittent failure in tests/benchmarks/timing_info #13073

andrewboie opened this issue Feb 5, 2019 · 1 comment
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@andrewboie
Copy link
Contributor

Seen on qemu_cortex_m3

***** Booting Zephyr OS zephyr-v1.13.0-4131-gc503eae198 *****
starting test - Time Measurement
Timing Results: Clock Frequency: 12 MHz
Context switch                               : 770 cycles , 64166 ns
Thread Creation                              :1419 cycles , 118250 ns
Thread cancel                                :1565 cycles , 130416 ns
Thread abort                                 :4411 cycles , 367583 ns
Thread Suspend                               :1660 cycles , 138333 ns
Thread Resume                                :1192 cycles , 99333 ns
Thread Sleep                                 :1726 cycles , 143833 ns
Heap Malloc                                  : 168 cycles , 14000 ns
Heap Free                                    : 150 cycles , 12500 ns
***** USAGE FAULT *****
  Illegal load of EXC_RETURN into PC
***** Hardware exception *****
Current thread ID = 0x20000638
Faulting instruction address = 0x0
Fatal fault in thread 0x20000638! Aborting.
***** HARD FAULT *****
  Fault escalation (see below)
***** USAGE FAULT *****
  Illegal use of the EPSR
***** Hardware exception *****
Current thread ID = 0x20000638
Faulting instruction address = 0x20000688
Fatal fault in thread 0x20000638! Aborting.
@andrewboie andrewboie added the bug The issue is a bug, or the PR is fixing a bug label Feb 5, 2019
@nashif nashif added the priority: low Low impact/importance bug label Feb 19, 2019
@andyross
Copy link
Contributor

andyross commented Mar 6, 2019

Yeah, as with others, this is a test that I can't make fail on unloaded systems across hundreds of runs. It's part of the broader symptoms well captured by #12553, and not really an issue with the test per se. Closing the test-specific bug.

@andyross andyross closed this as completed Mar 6, 2019
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 priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants